> will we be able to identify them once rewritten?
> Yes [:a | nil] ?
> or [:a| ]
Well actually we could use this rewrite rule:
RBParseTreeRewriter new
replace: '[ :`arg :`@args | ]' withValueFrom: [ :block |
block body
addNode: block arguments last;
parent ];
yourself
It replaces all occurrences of empty blocks with one or more
parameters with one that returns the the last argument. Like this we
ensure the correct behavior for all existing code in the image even if
we change the compiler to always return nil.
>> I will have to check all 60 empty blocks with arguments one by one.
>> Most of them are used in exception handlers that do not use the return
>> result, so this should mostly be a non-issue.
>
> I would :)
> but let us see what the others think for now.
>
> Lukas I'm still lookfing for the _ => := changes :)
Ok, I will provide a fix for Pharo 1.1 this morning.
Then we have to figure out later how the Refactoring Engine, Shout and
friends know how to parse.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Locked
