4 Apr
2013
4 Apr
'13
2:48 a.m.
privateState is meant to be used for FAMIX extensions.
hasClassScope should be used through an instance variable. There is no real benefit of not
having it.
Could you please open an issue?
Cheers,
Doru
On Apr 3, 2013, at 7:36 PM, Nicolas Anquetil <Nicolas.Anquetil(a)inria.fr> wrote:
then another question:
is there a logic behind the decision to use privateState or instance variables?
is it to save memory (as I understood from the mooseBook: "MinimalState")
But if so, is it really needed for something like a boolean (hasClassScope)?
nicolas
On 04/03/2013 05:55 PM, Tudor Girba wrote:
--
www.tudorgirba.com
"Things happen when they happen,
not when you talk about them happening."
No, it is not.
privateState is not a meta-model property. It is only an implementation issue to offer
state extensions in Pharo.
Cheers,
Doru
On Apr 3, 2013, at 5:43 PM, Anne Etien <anne.etien(a)univ-lille1.fr> wrote:
--
Nicolas Anquetil -- RMod research team (Inria)
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi,
Shouldn't the hasClassScope property of FAMIXMethod be declared as <derived>?
It is computed from privateState just as isConstructor or declaredExceptions which are
derived.
Same question for timeStamp.
Thanks in advance.
Anne
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Presenting is storytelling."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev