Re: [Pharo-dev] Design pattern for wrapper/proxy objects?

Hi Luke, Not only for the details of a particular proxy implementation like Ghost, but also because of all the discussions around it, I think this journal paper [1] we wrote may be of help to you. Cheers, [1] https://hal.inria.fr/hal-01081236 On Mon, Dec 4, 2017 at 5:51 AM, Luke Gorrie

Re: [Pharo-dev] Design pattern for wrapper/proxy objects?

Thanks Ben & Henrik for the ideas! I will scratch my head a bit and then try to do something sensible. :-)

Re: [Pharo-dev] Design pattern for wrapper/proxy objects?

For proxies/wrappers, you might want to look into how the Ghost framework interrupts sends. (I don't know the exact details, but I'd guess step 1 is subclassing ProtoObject, rather than Object) For your specific case, isn't there already a *Struct class in the image you can subclass, create a

Re: [Pharo-dev] Design pattern for wrapper/proxy objects?

On 4 December 2017 at 00:10, Luke Gorrie wrote: > Howdy, > > I have some Smalltalk objects that represent external data and I am looking > for a neat way to access them. > > The data that I am dealing with is C binary objects described by DWARF > schemas. So I will load a type

[Pharo-dev] Design pattern for wrapper/proxy objects?

Howdy, I have some Smalltalk objects that represent external data and I am looking for a neat way to access them. The data that I am dealing with is C binary objects described by DWARF schemas. So I will load a type declaration like this: struct outer { struct inner { int a, b; }; };