FAMIXAssociation>>SourceAnchor

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

FAMIXAssociation>>SourceAnchor

Nicolas Anquetil

FAMIXAssociations being SourcedEntities have a 'sourceAnchor' instance variable.

However it redefines the method sourceAnchor :

    ^ self from sourceAnchor

I am sure there was some good reason to do this, but to me this is counter intuitive and something should probably be corrected.

(in practice I spent from 11pm to 1am yesterday looking for a bug that did not exist :-( )

nicolas

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: FAMIXAssociation>>SourceAnchor

Tudor Girba-2
Hi,

Indeed, this is because importers did not provide source anchors for associations. So, we just picked the best approximation for practical reasons.

The reason for not exporting source anchors for associations is scalability: associations account for some 70% of the amount of objects in the model. Adding a source anchor for each of them increases significantly the size.

Cheers,
Doru


On Tue, Oct 18, 2011 at 1:27 PM, Nicolas Anquetil <[hidden email]> wrote:

FAMIXAssociations being SourcedEntities have a 'sourceAnchor' instance variable.

However it redefines the method sourceAnchor :

    ^ self from sourceAnchor

I am sure there was some good reason to do this, but to me this is counter intuitive and something should probably be corrected.

(in practice I spent from 11pm to 1am yesterday looking for a bug that did not exist :-( )

nicolas

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--
--

"Every thing has its own flow"


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: FAMIXAssociation>>SourceAnchor

Nicolas Anquetil
sure
but why not just let it return nil if there is nothing to return?

nicolas


De: "Tudor Girba" <[hidden email]>
À: "Moose-related development" <[hidden email]>
Envoyé: Mardi 18 Octobre 2011 13:35:14
Objet: [Moose-dev] Re: FAMIXAssociation>>SourceAnchor

Hi,

Indeed, this is because importers did not provide source anchors for associations. So, we just picked the best approximation for practical reasons.

The reason for not exporting source anchors for associations is scalability: associations account for some 70% of the amount of objects in the model. Adding a source anchor for each of them increases significantly the size.

Cheers,
Doru


On Tue, Oct 18, 2011 at 1:27 PM, Nicolas Anquetil <[hidden email]> wrote:

FAMIXAssociations being SourcedEntities have a 'sourceAnchor' instance variable.

However it redefines the method sourceAnchor :

    ^ self from sourceAnchor

I am sure there was some good reason to do this, but to me this is counter intuitive and something should probably be corrected.

(in practice I spent from 11pm to 1am yesterday looking for a bug that did not exist :-( )

nicolas

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--
--

"Every thing has its own flow"


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev