Brixey: They noticed a serious bug a few years ago where the result of a p***word check came non-normalised from memcmp
Audirsch: So you could try random p***words and it would just work every thousand times or so.
Gerrero: Scheppe: boolean false
Feerick: Thats true everywhere
Gerrero: Scheppe: IEEE floating point – Wikipedia, the free encyclopedia https://en.wikipedia.org/wiki/IEEE_floating_point
Best: Hmm I thought I do understand the concept but turns out it’s more than that lol I don’t seem to understand inheritance vs prototype difference. don’t they pretty much do the same thing?
Deridder: Prototyping is a form of inheritance.
Jeschke: You mean prototypal inheritance vs cl***ical cl***es
Glidden: Extending cl***es is another form of inheritance
Feerick: You can do cl***ical inheitance with prototypes
Feerick: But prototypes are more flexible
Rattner: Ahh I got it totally confused. so are inheritance is different concept to prototype?
Sneary: That’s not what anyone said.
Yusef: That sounds like what you initially said.
Halper: Actually, nvm, noone said that.
Legassie: Let me try to show an example of what Im talking about
Linsey: Inheritance is . when you create something that inherits from something else.
Armson: Prototyping is when you create an object that inherits from another object.
Guidi: AramKaram: “inheritance” and “prototype” are different concepts. “inheritance” just means “X gets parts of Y.” “prototype” means “an object that *happens* to be used as a starting point for creating other objects.” Anything can be a prototype. A prototype exists because inheritance exists, but they’re two separate things.
Woodin: Node-restful looks so much better than restify
Cosio: Some people calls “prototypes” by the name “exemplars” instead. Meaning that prototypes/examplars are just examples of objects you could have. You can then take that prototype/exemplar, clone it this is where inheritance kicks in, and change whatever you need in the clone.
Przybyla: Ah, it makes more sense as I read, I probably need just to practice with them to get a real life sense of them, but yeah I definitely sees what you Mean though
Emig: AramKaram: where do you read about JS or prototyping as a source?
Lauchaire: I’m using a for loop to add tabs to a page for each item in an array. I use var tab = do***ent.createElement to create the tab in a variable, then I use tabBar.appendChildtab to add it to the tab bar. But how can I add an click event listener to each tab to call a function with the tab’s title as an argument when it’s clicked?
Josilowsky: Where I’m not yet into it to be honest, Im just getting into OOP part of JS cause Im myself mostly interested in FP, so for now I’m trying to figure out all this inheritance and prorotyping topics, because fairly I don’t even distinguish these concepts to one another
Mariani: Keavon: Attach the handler to a parent of the tabs. Check to see which tab if any initiated the event via the “target” property, and then call the function based on that.
Mariani: That way you only have a single handler to worry about, not one per tab.
Garofalo: Ah, that makes sense.
Genuario: OO in JS is pretty meh anyway. You don’t lose much from not using it.
Rappe: Havvy: So the syntax is like this?
Skains: TabBar.addEventListener”click”, functione
Tinklenberg: And I check e.target?
Werremeyer: Http://pastebin.com/5ahvc9pa – how can I have that run only if $table doesnt already exist and if it does just replace the information?
Bodley: I mean, objects and dynamic dispatch are useful. But common OO idioms/patterns are not really
Moothart: I have a DOM element which contains an IMG tag followed by text. How can I get just that text?