It's a compiler bug. The compiler doesn't handle this case.
Let's summarize. Squeak doesn't handle proper an assignment to a block argument and it is a bug. But anyway, assignment to a block argument is considered bad practice so let's just forbid assignment to a block argument thus get rid of the bug. That is "Scanner allowBlockArgumentAssignment: false" is used for.
Is it right? And does other ST implementations follow the same way? I've checked: Pharo2.0 does not allow and Pharo3.0 does allow assignment to block argument. VA Smalltalk doesn't allow changing block arguments (thanks Louis)
-- View this message in context: http://forum.world.st/Modify-block-closure-parameters-tp4702118p4702700.html Sent from the Squeak - Beginners mailing list archive at Nabble.com.