8 Oct
2008
8 Oct
'08
10:12 p.m.
Hi
what is FMMultivalueLink?
parentClass: aType
parentClass := FMMultivalueLink on: self
update: #attributes
from: self parentClass
to: aType
parentClass set: aType
I'm probably too stupid to understand but let us try.
I do not understand why at the metamodel level I need to have in the
runtime
objects of the metametamodel.
Long long time ago I did a stupid code generator that took a stupid
MMModel
and generated plain code for the metamodel. Why this is not like that
with FAMIX30
in the latest version?
why do we trade space **and** speed for a meta stuff?
So do I have to code a code generator?
Or just replace all the FMMultivalueLink myself?
I'm confused I thought that the new FAME was better.
Stef
9 Oct
9 Oct
11:28 a.m.
I assume this is the replacement for opposite slots by Adrian which does
exactly -not- increase space used and decrease speed. It is put where
you would put a collection for your objects anyway (since its
multivalued) and where you use the API for collections on that object;
it automatically updates the other side. I don't see how you can
implement this more optimally.
Correct me if I'm wrong, it's Adrian's code, not mine.
cheers,
Stéphane Ducasse wrote:
Hi
what is FMMultivalueLink?
parentClass: aType
parentClass := FMMultivalueLink on: self
update: #attributes
from: self parentClass
to: aType
parentClass set: aType
I'm probably too stupid to understand but let us try.
I do not understand why at the metamodel level I need to have in the
runtime
objects of the metametamodel.
Long long time ago I did a stupid code generator that took a stupid
MMModel
and generated plain code for the metamodel. Why this is not like that
with FAMIX30
in the latest version?
why do we trade space **and** speed for a meta stuff?
So do I have to code a code generator?
Or just replace all the FMMultivalueLink myself?
I'm confused I thought that the new FAME was better.
Stef
11:35 a.m.
Hi,
Indeed, as far as I saw the FMMultivalueLink is nothing but a smarter
collection that also takes care of updating the opposites.
If for some reason we will not like it anymore, we will be able to
replace them with Collection, and the rest of the code should work
just the same. So, I do not see a problem with this.
Doru
On Oct 9, 2008, at 11:28 AM, Toon Verwaest wrote:
I assume this is the replacement for opposite slots by
Adrian which
does
exactly -not- increase space used and decrease speed. It is put where
you would put a collection for your objects anyway (since its
multivalued) and where you use the API for collections on that object;
it automatically updates the other side. I don't see how you can
implement this more optimally.
Correct me if I'm wrong, it's Adrian's code, not mine.
cheers,
Stéphane Ducasse wrote:
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Next time you see your life passing by, say 'hi' and get to know her."
Hi
what is FMMultivalueLink?
parentClass: aType
parentClass := FMMultivalueLink on: self
update: #attributes
from: self parentClass
to: aType
parentClass set: aType
I'm probably too stupid to understand but let us try.
I do not understand why at the metamodel level I need to have in the
runtime
objects of the metametamodel.
Long long time ago I did a stupid code generator that took a stupid
MMModel
and generated plain code for the metamodel. Why this is not like that
with FAMIX30
in the latest version?
why do we trade space **and** speed for a meta stuff?
So do I have to code a code generator?
Or just replace all the FMMultivalueLink myself?
I'm confused I thought that the new FAME was better.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3 p.m.
Ok now I understand.
The name was really confusing for me.
Hi,
Indeed, as far as I saw the FMMultivalueLink is nothing but a
smarter collection that also takes care of updating the opposites.
If for some reason we will not like it anymore, we will be able to
replace them with Collection, and the rest of the code should work
just the same. So, I do not see a problem with this.
Doru
On Oct 9, 2008, at 11:28 AM, Toon Verwaest wrote:
I assume this is the replacement for opposite
slots by Adrian which
does
exactly -not- increase space used and decrease speed. It is put where
you would put a collection for your objects anyway (since its
multivalued) and where you use the API for collections on that
object;
it automatically updates the other side. I don't see how you can
implement this more optimally.
Correct me if I'm wrong, it's Adrian's code, not mine.
cheers,
Stéphane Ducasse wrote:
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Next time you see your life passing by, say 'hi' and get to know
her."
Hi
what is FMMultivalueLink?
parentClass: aType
parentClass := FMMultivalueLink on: self
update: #attributes
from: self parentClass
to: aType
parentClass set: aType
I'm probably too stupid to understand but let us try.
I do not understand why at the metamodel level I need to have in the
runtime
objects of the metametamodel.
Long long time ago I did a stupid code generator that took a stupid
MMModel
and generated plain code for the metamodel. Why this is not like
that
with FAMIX30
in the latest version?
why do we trade space **and** speed for a meta stuff?
So do I have to code a code generator?
Or just replace all the FMMultivalueLink myself?
I'm confused I thought that the new FAME was better.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
2:59 p.m.
Ok thanks I understand now.
Indeed if this is for collection it make sense.
Stef
On Oct 9, 2008, at 11:28 AM, Toon Verwaest wrote:
I assume this is the replacement for opposite slots by
Adrian which
does exactly -not- increase space used and decrease speed. It is put
where you would put a collection for your objects anyway (since its
multivalued) and where you use the API for collections on that
object; it automatically updates the other side. I don't see how you
can implement this more optimally.
Correct me if I'm wrong, it's Adrian's code, not mine.
cheers,
Stéphane Ducasse wrote:
Hi
what is FMMultivalueLink?
parentClass: aType
parentClass := FMMultivalueLink on: self
update: #attributes
from: self parentClass
to: aType
parentClass set: aType
I'm probably too stupid to understand but let us try.
I do not understand why at the metamodel level I need to have in
the runtime
objects of the metametamodel.
Long long time ago I did a stupid code generator that took a stupid
MMModel
and generated plain code for the metamodel. Why this is not like
that with FAMIX30
in the latest version?
why do we trade space **and** speed for a meta stuff?
So do I have to code a code generator?
Or just replace all the FMMultivalueLink myself?
I'm confused I thought that the new FAME was better.
Stef
5682
days inactive
5683
days old
4 comments
3 participants
participants (3)
-
Stéphane Ducasse -
Toon Verwaest -
Tudor Girba