[Vm-dev] Re: [squeak-dev] Re: [Pharo-project] problem with
tempNamed: in Pharo 2.0
Mariano Martinez Peck
marianopeck at gmail.com
Tue May 1 20:53:40 UTC 2012
>>> But tempNames is fundamentally broken for closures.
>> Just to avoid confusing, #tempNames itself looks correct:
>> "Answer a SequenceableCollection of the names of the receiver's
>> variables, which are strings."
>> ^ self debuggerMap tempNamesForContext: self
> Yes. That's for ContextPart. But it doesn't work for CompiledMethod,
> since temps may differ between a method and its blocks.
Right, but weren't we always talking about Contexts? Because #tempNames of
CompiledMethod is different than the thing of contexts, isn't it? It is
related to the method trailer. In fact, I have just checked Squeak 4.3 and
CompiledMethod does not even implement #tempNames. The implementation in
CompiledMethod >> #tempNames
self holdsTempNames ifFalse: [^#()].
^self tempNamesString subStrings: ' '
how would it be the correct implementation then?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev