3 May
2010
3 May
'10
2:31 p.m.
Yes, it is necessary because it is very often the case
that you need
access to the model from the entity. This is why we added it by
default to MooseElement.
But if you need to access the model from an entity, why not to have a
variable mooseModel in MooseElement instead?
One very good reason I see for having mooseID, is to circumvent the
hash limitation in Pharo. I am looking for another reason.
Alexandre
On 3 May 2010, at 00:13, Alexandre Bergel wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
I am wondering why MooseElement needs a mooseID. By looking at the
sender of mooseID, I can see methods like:
MooseModel>>includes: anItem
anItem isNil ifTrue: [^ false].
^ self includesID: anItem mooseID
and MooseModel class>>ownerOf: element that makes use of mooseID.
But is this really necessary?
Just wondering...
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Reasonable is what we are accustomed with."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev