Hi,

On Jan 4, 2016, at 6:30 PM, Cl��ment Bera <bera.clement@gmail.com> wrote:

Hello,

This is unrelated to Spur / SqueakV3 memory manager. The VM support has been there and stable for a long time now.

I tried to add those primitives in Pharo but the problem is that the debugger in Pharo uses EyeInspector whereas the inspectors are done with Glamour.

Hence, to add support for ProtoObject debugging you need:

- to make interpretation implemented in Context compliant

- to make EyeInspector compliant (for the inspector in the debugger)

- to make GTInspector compliant.

I am not sure I understand what you mean by " interpretation implemented in Context compliant���. Could you explain?

I already made GTInspector and GTDebugger work with ProtoObject once. I lost the changes in the meantime :), but I will redo them. The only thing I needed were these primitives. But, maybe I missed something.

Cheers,
Doru

Cheers !

Clement

2016-01-04 16:42 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:

Hi,

The VM (both Cog and Spur) supports basic manipulation of objects without relying on sending messages to those objects. These primitives are meant to be handled by methods in Context. Eliot provided a changeset with these methods, and they are not yet in Pharo:

object: anObject basicAt: index

object: anObject basicAt: index put: value

object: anObject eqeq: anOtherObject

object: anObject instVarAt: anIndex

object: anObject instVarAt: anIndex put: aValue

object: anObject perform: selector withArguments: argArray inClass: lookupClass

objectClass: anObject

objectSize: anObject

I added an issue and the slice:

https://pharo.fogbugz.com/f/cases/17313/Missing-primitive-methods-in-Context

As I note in the issue, I think it is certainly interesting to have a more powerful mirrors mechanism, but until then we should still be able to use what the VM already provides.

I would like to use these primitives now to make the GT Inspector and Debugger be able to work with ProtoObject. I thought these methods were supposed to be in the Spur version of Pharo, but it seems they are not. So, I am wondering if maybe I am not missing something. Am I missing something or should we integrate these methods?

Cheers,

Doru

--

www.tudorgirba.com

www.feenk.com

"Problem solving efficiency grows with the abstractness level of problem understanding."

--
www.tudorgirba.com
www.feenk.com

"Things happen when they happen,
not when you talk about them happening."