Hi James, 2010/8/30 James Ladd <james_ladd@hotmail.com>
Hi Eliot,
I cant use those thinks because im not in Smalltalk at the time, im in Java on the JVM.
Ah, OK. Now I understand.
(Did someone say 'challenge')
I thought about the store question in the shower this morning and I think it means take the top of the stack but dont pop it. Please let me know if Im wrong?
That's right. So... 140 10001100 kkkkkkkk jjjjjjjj Push Temp At kkkkkkkk In Temp Vector At: jjjjjjjj tempVector := activation localAt: kkkkkkkk. value := tempVector[jjjjjjjj]. activation push: value 141 10001101 kkkkkkkk jjjjjjjj Store Temp At kkkkkkkk In Temp Vector At: jjjjjjjj tempVector := activation localAt: kkkkkkkk. tempVector[jjjjjjjj] := activation stackTop. 142 10001110 kkkkkkkk jjjjjjjj Pop and Store Temp At kkkkkkkk In Temp Vector At: jjjjjjjj tempVector := activation localAt: kkkkkkkk. tempVector[jjjjjjjj] := activation stackTop. activation popStack. Clear? If so, I'd be very happy to improve my documentation based on your reading and my clarification. best, Eliot
Rgs, James.
Hi James,
perhaps you could use the implementations of ContextPart pushRemoteTemp:inVectorAt: popIntoRemoteTemp:inVectorAt: storeIntoRemoteTemp:inVectorAt: (& Interpreter pushRemoteTemp:inVectorAt: popIntoRemoteTemp:inVectorAt: if you have them to hand) as the spec and check the documentation. The intent is that k..k is the index of the temp containing the remote vector and j..j is the index in the remote temp vector.
cheers Eliot
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project