Fwd: Heap>>first broken?
stephane ducasse
stephane.ducasse at free.fr
Sun Sep 2 09:42:33 UTC 2007
I forwarded the mail to marcus since he does not read the list.
He is on vacation for a week so will certainly answer it later.
Stef
Begin forwarded message:
> From: Andreas Raab <andreas.raab at gmx.de>
> Date: 31 août 2007 05:22:52 HAEC
> To: The general-purpose Squeak developers list <squeak-
> dev at lists.squeakfoundation.org>
> Subject: Heap>>first broken?
> Reply-To: The general-purpose Squeak developers list <squeak-
> dev at lists.squeakfoundation.org>
>
> Hi -
>
> Just stumbled over this:
>
> self should:[Heap new first] raise: Error.
>
> Right? However, in Squeak 3.9 and later it doesn't. From the 3.9
> change log it appears it got introduced here:
>
> ------
> Change Set: decompileBlock-md
> Date: 24 November 2005
> Author: Marcus Denker
> A simplification for BlockContext>>decompileBlock:
> The Method got the tempNames by compiling the source of the
> method. This
> is already implemented in methodNode tempNames... thus not needed
> here.
> ------
> remove emptycheck for Heap>>fist and SequencableCollection
> #first, #last, #middle
> ------
>
> but no comment as to why. Any insights into the reasons for this
> change anyone?
>
> Cheers,
> - Andreas
>
>
More information about the Squeak-dev
mailing list
|