| || || |
| || |
| || || |
Not only does Lindley explain how most of the native Objects work (String, Number, Object, Function, etc.), he talks about user-defined objects and object constructors. He also talks about how objects work in the prototype chain, how inheritance works, and how variable references get resolved in the scope chain. He looks at how properties work - how they are set, gotten, and deleted. He talks about breaking out of function execution and about dynamically changing function execution context at runtime.
Looking For A New Job?
- IT Manager - ColdFusion/SQL web application developer at ARELLO
- DevOps Engineer at Linode
- Software Engineer at Linode
- Web Applications Developer (Remote / Telecommute) at SiteVision, Inc.
How old are these peop... (stops, looks around at coworkers)... nevermind.
@Matt, true dat:
Now that I know what's in Cody Lindley's book, I'm thinking about learning how to read.
thanks for the info - just bought one :-)
will dig into it!
hehehe... i'll admit i'm one of those developers. I'll make sure to pick up this book :)
I find it interesting that Cody didn't seem to include any date or copyright information on the book (not even the build-in tools that PDF's usually offer.)
Does he intend this to be some sort of Creative Commons thing?
(Cuz' if so, I'm totally sharing this with all my friends. ;-P)
My understanding is that, under current US copyright law, ALL creative expression is now intrinsically copyrighted, even if the author doesn't explicitly declare it copyrighted.
If you create a work that's derivative of a work protected by intrinsic copyright, it could be "innocent infringement". (You have the defense "I didn't know the author intended it to be copyrighted.") As I understand it, that's the purpose of "takedown notices". That is, you haven't committed a tort yet because copyright wasn't declared, but you have to take it down, now that you know it's copyrighted.
I'm not a lawyer. And some of that is word-of-mouth from intellectual property lawyers I've talked to (= second hand information, subject to miscommunication).
Also, I haven't bought the book yet, because I'm handling some work emergencies. So I don't know whether or not Cody said "You can use these snippets.". But in general, it's always safest to rely on one's own creative expression.