Re: "When closures capture their context" and "scope gotchas in Javascript"

Replies are listed 'Best First'.
Re^2: "When closures capture their context" and "scope gotchas in Javascript" by moritz (Cardinal) on Feb 08, 2008 at 16:57 UTC
Speaking of other language woes - I intended to learn Lua, until I found out that variables are global by default, and you have to add a keyword to limit their scope to the current sub/method. That, and the fact that I couldn't find a `use strict;` equivalent made me jump back to perl immediately.	[reply] [d/l]
Re^3: "When closures capture their context" and "scope gotchas in Javascript" by dragonchild (Archbishop) on Feb 09, 2008 at 02:12 UTC
Which happens to be the reason both tye and I have relegated Ruby to the "Neat Toy" category. If the compiler can't be enlisted to help you catch typos, then your language design is seriously flawed. (That and how does a language by a Japanese hacker go through 3 versions before an American adds support for UTF-8??) My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]
Re^4: "When closures capture their context" and "scope gotchas in Javascript" by Joost (Canon) on Feb 09, 2008 at 15:29 UTC
how does a language by a Japanese hacker go through 3 versions before an American adds support for UTF-8? IIRC Unicode isn't nearly as popular in Asia as it is in, for instance, western Europe. Last I heard (some years ago) the Chinese really didn't like it since they already use some kind of encoding that differentiates certain "characters" that look /exactly/ the same but are pronounced differently (which is useful for speech generation), and at least back then the unicode standard did not distinguish between them. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^5: "When closures capture their context" and "scope gotchas in Javascript" by dragonchild (Archbishop) on Feb 10, 2008 at 06:24 UTC
Re^5: "When closures capture their context" and "scope gotchas in Javascript" by Porculus (Hermit) on Feb 10, 2008 at 14:31 UTC
Re^3: "When closures capture their context" and "scope gotchas in Javascript" by Errto (Vicar) on Feb 08, 2008 at 18:49 UTC
I intended to learn Lua, until I found out that variables are global by default, and you have to add a keyword to limit their scope to the current sub/method. That's true in Perl too if you don't use `strict`. Well, so in Perl the alternative is lexical scope which, as I know from certain other ahemVBahem experience, is much better than subroutine scope for most purposes.	[reply] [d/l]