I would keep CompiledMethod
class>>primitive:numArgs:numTemps:stackSize:literals:bytecodes:trailer:, it
has some abstraction that could be useful for e.g. tests.  I like the
assurance that CompiledMethod flag is zero, and so am happy to sere that
deleted.  e.g. Cog has a mode controlled by vmParameterAt:put: where it will
set the flag bits of methods that are interpreted.  Craig has code in his
spoon VM which sets the flag for used methods.  I would like to reserve the
bit for introspective tasks like these, and for these it is convenient that
all methods have a zero flag bit.

cheers
Eliot

On Sun, Dec 13, 2009 at 8:05 AM, Igor Stasenko <siguctua at gmail.com> wrote:

> Hello guys,
>
> there are few unsent messages on class side of CompiledMethod,
>
> primitive: primNum numArgs: numArgs numTemps: numTemps stackSize:
> stackSize literals: literals bytecodes: bytecodes trailer:
> trailerBytes
> and
> newBytes: numberOfBytes trailerBytes: trailer nArgs: nArgs nTemps:
> nTemps nStack: stackSize nLits: nLits primitive: primitiveIndex flag:
> flag
>
> I checked both in Pharo 1.1-core and in Trunk images, both of them
> seem having no senders.
>
> Any insights if it safe to wipe them out?
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20091213/fdabe55a/attachment.htm