> You both agree that this is not a bug, them we have to ascertain that > 'average Smalltalker' will understand that using closures in Pharo > changes the Smalltalk language definition.
The point is Pharo finally has real closures and sane execution semantics. The same semantics that all other Smalltalk dialects already had for decades, and the same semantics that Lisp, Scheme and even Javascript programmers trusted on in the last 40 years. The previous block semantics on Pharo (and Squeak) were completely broken. The 'average Smalltalker' had to understand how contexts were setup and how the source is compiled to bytecode to explain the numerous hacks that were required for example in get the blocks behave sanely in Seaside. This is no longer necessary. The 'average Smalltalker' can just read the wikipedia page on closures. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
