With behavior of BL break/continue depended upon internal impl details (whether they use ctl stmts or BKs) of enclosing ctl abstractions
-
-
Yes done deal. Mostly showing that considerable thought+experience preceded decisions.
-
I don't buy the idea that JS is *so* different from Smalltalk and Ruby. Ruby has C-style control flow too.
-
Ruby has lambda vs http://Proc.new gratuitous split. Also Ruby far from static C in semantics. I gave Block Lambdas my best shot.
-
Gratuitous split but maybe worth it.
-
Unfalsifiable faith-article. Consider C switch fall through hazard, real world comp.risks cost. Ruby dead frame return throw bug experience?
-
Very little dead frame return issues. Has to do with whether you're taught blocks as functions or something else.
-
Dead frames not the problem. Instead a layering issue wrt nested user and language defined ctl abstractions. Some day I'll show you
-
I know the issue about `break` needing N frames depending on how layered the abstraction is. Is that what you mean?
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.