Earlier quoted context omitted.
Agreed, but the name is Crockford. His site, which has a bunch of interesting JavaScript links on it: http://crockford.com
Woops my bad, apologies to Mr. Crockford.
The best JavaScript guide ever
51–56 of 56 posts
Re: The best JavaScript guide ever
#52I like John Resig's tutorial: http://ejohn.org/apps/learn/
Re: The best JavaScript guide ever
#53Earlier quoted context omitted.
Yes, as several people have mentioned, I should have said block scope . JS does allow for blocks, but they don't work the way the parent was thinking. You can toss extra curly braces in the code and it is a "block" but unless they are preceded by an "if", "for", or something similar, they don't do much. They do not return values and they do not affect variable scope. Functions do both, hence my last example.
I think my understanding of blocks is fine. "Returning" was the wrong expression, I meant the value of a script (like the result of an eval). I am aware of the lack of block scope in JS :-)
Re: The best JavaScript guide ever
#54Re: The best JavaScript guide ever
#55Or apparently, on the Processing XML with E4X page, there are errors in the page: /content/body/div[2]/pre[1]/@function, reference to undefined name 'syntax': line 1, column 1 where every code sample should be.
It's under a CC license, so I am hoping that someone will make a better interface for the content some day.