> On 17 Mar 2022, at 18:00, Esteban Maringolo wrote:
>
> That is great!
>
> Is it possible to disable it for doits and other playground expressions?
>
No, there is no hook yet… it would be interesting to see how to do that.
(e.g. per playground compiler parameters, parameters for doit indep
> My *concern* with inlining is that since it is designed to short-circuit
> dynamic method lookup, it is impossible to call a *different* implementation.
> That is, you lose the opportunity to have the *receiver* decide how to
> respond to the message. You may think of it as a message, but the
> My chief concern is that I am a bear of very little brain,
> and if you change the meaning of #isNil to anything at all
> other than "is the receiver identical to nil" you *WILL*
> (not may) confuse me.
I can understand your probably well-justified concern that power can always be
misused. I
> What you can do is turning it off globally in the setting (all compiler
> option are listed there)
>
> But take care: we can not recompile the image without optimzations as this
> adds intererrupt possibilities to code that was not
> interruptable before, which breaks the code in for process sw
I feel like you’ve latched onto something that is genuinely a non problem and
if you get your way we all suffer reduced performance and a guarantee that a
nil test is universally the same thing.
If you want an overridable nil test, write your own nil test like isNilish and
make it mean what you
> I feel like you’ve latched onto something that is genuinely a non problem…
I wouldn’t call complexity and lack of consistency a “non problem”, but it
sounds like for you the practical implications outweigh my
seemingly-somewhat-ideological/niche concerns. Is that a fair summary? In any
case,
What, exactly, is inconsistent about a key message isNil being allowed to be
overridden?
There is a VERY simple solution to your problem that does not involve
disrupting the platform.
But you'd rather change the platform.
Part of the reason Smalltalk has not been the greatest platform to bui
On Fri, Mar 18, 2022 at 3:24 PM Todd Blanchard via Pharo-users
wrote:
>
> What, exactly, is inconsistent about a key message isNil being allowed to be
> overridden?
Overrides are not the issue here.
> There is a VERY simple solution to your problem that does not involve
> disrupting the platfo
> On Mar 18, 2022, at 11:39 AM, Esteban Maringolo wrote:
>
> You say that Smalltalk is not so hot for system developments because
> it's extremely malleable? What are you measuring it against?
Lots of things but to keep things simple lets go with Objective C since it is
quite similar in conc
