[Vm-dev] Processor association in special objects array

[Guillermo Polito]

On Wed, May 30, 2012 at 7:25 PM, Igor Stasenko <siguctua at gmail.com> wrote:

>
> On 30 May 2012 18:42, Guillermo Polito <guillermopolito at gmail.com> wrote:
> >
> >
> > On Wed, May 30, 2012 at 6:32 PM, Nicolas Cellier <
> nicolas.cellier.aka.nice at gmail.com> wrote:
> >>
> >>
> >> Doesn't it enable creation of a new Processor ?
> >
> >
> > Maybe (not sure about this), but why does this design decision apply for
> this object only?
>
> Because! :)
> Hell i know why.. a proper answer would probably be that different
> parts are done at different time
> by different people without good communication &/ striving for unified
> interfaces.
>

That's a good enough reason :).

Thanks to all!


> > Because for other objects I have to recreate the complete array :/.
> >
> >>
> >>
> >> Nicolas
> >>
> >> 2012/5/30 Guillermo Polito <guillermopolito at gmail.com>:
> >> >
> >> > Hi!
> >> >
> >> > With Ben we were wandering the reason why the special objects array
> points to the association #Processor->Processor, and not directly to the
> Processor object.
> >> >
> >> > TIA,
> >> > Guille & Ben
> >> >
> >
> >
> >
>
>
>
> --
> Best regards,
> Igor Stasenko.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20120530/c7d1bcd4/attachment-0001.htm