Nicolas, Sig, The problem is compiler inlining? That happens at compile time, right? :) Unless I am missing something, I see no reason to get upset about what you propose. The runtime cost from the added messages is decided when the code is compiled, and things that are currently inlined would go right on being that way, even after they are recompiled?? Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua@gmail.com] Sent: Sunday, October 10, 2010 9:06 AM To: The general-purpose Squeak developers list Cc: Pharo Development Subject: Re: [Pharo-project] [squeak-dev] Compiler pedantic about ifNotNil: argument On 10 October 2010 15:39, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
The compiler uselessly insist on #ifNotNil: argument being a zero/one arg block. Thus we cannot write this xtream sentence
process ifNotNil: #terminate.
When the argument is not a block, Compiler should avoid inlining and just send a normal message.
+1 i am also missing: someThing ifTrue: 1 ifFalse: 0
cheers
Nicolas
-- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project