Smalltalk › Frameworks & Tools › Moose

Re: Request to Join Project Verveine J

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Tudor Girba

Re: Request to Join Project Verveine J

Hi Nicolas,

Thanks for getting me access to the project. I will try to look into it in the following year.

next is a derived property. You should only save the previous pointer.

The context of next/previous is the context of the scope in which the association is defined. Thus, for example, for invocations, the scope is the sender method. For inheritance, the scope is the class.

Cheers,
Doru

On 20 Dec 2010, at 18:38, Nicolas Anquetil wrote:

>
>
> ----- Mail transféré -----
>> De: "Nicolas Anquetil" <[hidden email]>
>> À: [hidden email]
>> Envoyé: Lundi 20 Décembre 2010 18:28:49
>> Objet: Re: Request to Join Project Verveine J
>> Done,
>>
>> By the way, I looked at the next/previous Association
>> Moose impoter does not support it yet.
>> It is stated in the comments, and the next: method is not implemented.
>> Any special reason for this?
>>
>> Also, what's the semantics? It's inside a method / inside a class ?
>>
>>
>> nicolas
>>
>> ----- Mail original -----
>>> De: [hidden email]
>>> À: "nicolas anquetil" <[hidden email]>
>>> Envoyé: Lundi 20 Décembre 2010 18:16:16
>>> Objet: Request to Join Project Verveine J
>>> Tudor Girba has requested to join your project.
>>> You can approve this request here:
>>> https://gforge.inria.fr/project/admin/?group_id=2934
>>>
>>> Comments by the user:
>>> Would it be possible to give me access to the sources?
>>>
>>> Cheers,
>>> Doru

--
www.tudorgirba.com

"Being happy is a matter of choice."

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

Nicolas Anquetil

Re: Request to Join Project Verveine J

----- Mail original -----

> De: "Tudor Girba" <[hidden email]>
> À: "Nicolas Anquetil" <[hidden email]>
> Cc: "Moose-dev Moose Dev" <[hidden email]>
> Envoyé: Mercredi 22 Décembre 2010 12:00:28
> Objet: Re: Request to Join Project Verveine J
> Hi Nicolas,
>
> Thanks for getting me access to the project. I will try to look into
> it in the following year.
>
> next is a derived property. You should only save the previous pointer.

yes, but FAMIXAssociation>>previous: calls FAMIXAssociation>>next: which does not exist.
So the question remains: Is it supposed to work?
As this seems to be a pretty basic thing lacking here ...

> The context of next/previous is the context of the scope in which the
> association is defined. Thus, for example, for invocations, the scope
> is the sender method. For inheritance, the scope is the class.

OK for the invocation and access and reference.
But What would mean a next/previous for inheritance? Is it only for multiple inheritance?

nicolas

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

Tudor Girba

Re: Request to Join Project Verveine J

Hi,

Indeed, this was a bug. I fixed it in the latest Famix-Core.

Regarding the inheritance, it is about the order of multiple inheritance, but it is also about the order of implements/extends in Java.

Cheers,
Doru

On 22 Dec 2010, at 21:16, Nicolas Anquetil wrote:

>
> ----- Mail original -----
>> De: "Tudor Girba" <[hidden email]>
>> À: "Nicolas Anquetil" <[hidden email]>
>> Cc: "Moose-dev Moose Dev" <[hidden email]>
>> Envoyé: Mercredi 22 Décembre 2010 12:00:28
>> Objet: Re: Request to Join Project Verveine J
>> Hi Nicolas,
>>
>> Thanks for getting me access to the project. I will try to look into
>> it in the following year.
>>
>> next is a derived property. You should only save the previous pointer.
>
> yes, but FAMIXAssociation>>previous: calls FAMIXAssociation>>next: which does not exist.
> So the question remains: Is it supposed to work?
> As this seems to be a pretty basic thing lacking here ...
>
>> The context of next/previous is the context of the scope in which the
>> association is defined. Thus, for example, for invocations, the scope
>> is the sender method. For inheritance, the scope is the class.
>
> OK for the invocation and access and reference.
> But What would mean a next/previous for inheritance? Is it only for multiple inheritance?
>
> nicolas

--
www.tudorgirba.com

"There are no old things, there are only old ways of looking at them."

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