Code Generator - Moose-dev - INF Mailman

List overview All Threads
Download

Code Generator

files and folders problem

EMOF.Comment

sellossa＠ensieta.fr

21 May 2007 21 May '07

2:28 p.m.

hi! I am still working on the code generator in Moose. With the BasicCodeGenerator class, you generate a metamodelling protocol for each attribute of a EMOF class What is the use of these "metamodel methods" ? thanks Sara

Reply

Show replies by thread

Adrian Kuhn

21 May 21 May

10 p.m.

Hey sara, that are the meta-annotations that META uses to build des metamodel for the classes. See for example FAMIXMethod, or any other famix class, to learn how this is used. Also you may find some slides on my website http://www.iam.unibe.ch/~akuhn/Documents/Slides/2006-Moose-GoingMeta.pdf cheers, AA On 21 May 2007, at 14:28 , sellossa(a)ensieta.fr wrote:

hi! I am still working on the code generator in Moose. With the BasicCodeGenerator class, you generate a metamodelling protocol for each attribute of a EMOF class What is the use of these "metamodel methods" ? thanks Sara _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply

sellossa＠ensieta.fr

22 May 22 May

10:10 a.m.

thank you for your answer. By the way, did you see the problem that occurs when the BasicCodeGenerator is used to generate code from a model that contain a package with subpackages ? thanks Sara

Hey sara, that are the meta-annotations that META uses to build des metamodel for the classes. See for example FAMIXMethod, or any other famix class, to learn how this is used. Also you may find some slides on my website http://www.iam.unibe.ch/~akuhn/Documents/Slides/2006-Moose-GoingMeta.pdf cheers, AA On 21 May 2007, at 14:28 , sellossa(a)ensieta.fr wrote:

hi! I am still working on the code generator in Moose. With the BasicCodeGenerator class, you generate a metamodelling protocol for each attribute of a EMOF class What is the use of these "metamodel methods" ? thanks Sara _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply

Adrian Kuhn

12:22 p.m.

Yes, that's a know limitation at the moment. The problem is that it is not so much code generation but more META which is affected by this, but it is on my todo list. For the moment, I can only ask you to workaround this by not using subpackages. cheers, AA On 22 May 2007, at 10:10 , sellossa(a)ensieta.fr wrote:

thank you for your answer. By the way, did you see the problem that occurs when the BasicCodeGenerator is used to generate code from a model that contain a package with subpackages ? thanks Sara

Hey sara, that are the meta-annotations that META uses to build des metamodel for the classes. See for example FAMIXMethod, or any other famix class, to learn how this is used. Also you may find some slides on my website http://www.iam.unibe.ch/~akuhn/Documents/Slides/2006-Moose- GoingMeta.pdf cheers, AA On 21 May 2007, at 14:28 , sellossa(a)ensieta.fr wrote:

hi! I am still working on the code generator in Moose. With the BasicCodeGenerator class, you generate a metamodelling protocol for each attribute of a EMOF class What is the use of these "metamodel methods" ? thanks Sara _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply

sellossa＠ensieta.fr

3:29 p.m.

ok But I've already tried to fix this problem in my own code generator. To sum up, I 've created a visitor called DomainCodeGenerator that inherits directly from your BasicCodeGenerator. Then, I 've taken your method visitPackage and I 've changed it a little bit in my own class. In my version, I do not visit the nesting package any more because it has been already visited before. I have tested my code generator with differents EMOF models and it seems to work :) Do you think that my solution is correct ? I can publish my package if you want to have a look on this thanks sara

Yes, that's a know limitation at the moment. The problem is that it is not so much code generation but more META which is affected by this, but it is on my todo list. For the moment, I can only ask you to workaround this by not using subpackages. cheers, AA On 22 May 2007, at 10:10 , sellossa(a)ensieta.fr wrote:

thank you for your answer. By the way, did you see the problem that occurs when the BasicCodeGenerator is used to generate code from a model that contain a package with subpackages ? thanks Sara

Hey sara, that are the meta-annotations that META uses to build des metamodel for the classes. See for example FAMIXMethod, or any other famix class, to learn how this is used. Also you may find some slides on my website http://www.iam.unibe.ch/~akuhn/Documents/Slides/2006-Moose- GoingMeta.pdf cheers, AA On 21 May 2007, at 14:28 , sellossa(a)ensieta.fr wrote:

hi! I am still working on the code generator in Moose. With the BasicCodeGenerator class, you generate a metamodelling protocol for each attribute of a EMOF class What is the use of these "metamodel methods" ? thanks Sara _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply

Adrian Kuhn

4:07 p.m.

Yes, please publish it. I'll have a look Thursday. cheers, AA On 22 May 2007, at 15:29 , sellossa(a)ensieta.fr wrote:

ok But I've already tried to fix this problem in my own code generator. To sum up, I 've created a visitor called DomainCodeGenerator that inherits directly from your BasicCodeGenerator. Then, I 've taken your method visitPackage and I 've changed it a little bit in my own class. In my version, I do not visit the nesting package any more because it has been already visited before. I have tested my code generator with differents EMOF models and it seems to work :) Do you think that my solution is correct ? I can publish my package if you want to have a look on this thanks sara

Yes, that's a know limitation at the moment. The problem is that it is not so much code generation but more META which is affected by this, but it is on my todo list. For the moment, I can only ask you to workaround this by not using subpackages. cheers, AA On 22 May 2007, at 10:10 , sellossa(a)ensieta.fr wrote:

thank you for your answer. By the way, did you see the problem that occurs when the BasicCodeGenerator is used to generate code from a model that contain a package with subpackages ? thanks Sara

Hey sara, that are the meta-annotations that META uses to build des metamodel for the classes. See for example FAMIXMethod, or any other famix class, to learn how this is used. Also you may find some slides on my website http://www.iam.unibe.ch/~akuhn/Documents/Slides/2006-Moose- GoingMeta.pdf cheers, AA On 21 May 2007, at 14:28 , sellossa(a)ensieta.fr wrote: > hi! > > I am still working on the code generator in Moose. > With the BasicCodeGenerator class, you generate a metamodelling > protocol > for each attribute of a EMOF class > What is the use of these "metamodel methods" ? > > thanks > > Sara > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply

sellossa＠ensieta.fr

4:23 p.m.

It is done ! the package is called Meta-DomainGenerator. It contains the DomainCodeGenerator class and all the tests. the package is published under my name: sellos Sara

Yes, please publish it. I'll have a look Thursday. cheers, AA On 22 May 2007, at 15:29 , sellossa(a)ensieta.fr wrote:

ok But I've already tried to fix this problem in my own code generator. To sum up, I 've created a visitor called DomainCodeGenerator that inherits directly from your BasicCodeGenerator. Then, I 've taken your method visitPackage and I 've changed it a little bit in my own class. In my version, I do not visit the nesting package any more because it has been already visited before. I have tested my code generator with differents EMOF models and it seems to work :) Do you think that my solution is correct ? I can publish my package if you want to have a look on this thanks sara

Yes, that's a know limitation at the moment. The problem is that it is not so much code generation but more META which is affected by this, but it is on my todo list. For the moment, I can only ask you to workaround this by not using subpackages. cheers, AA On 22 May 2007, at 10:10 , sellossa(a)ensieta.fr wrote:

thank you for your answer. By the way, did you see the problem that occurs when the BasicCodeGenerator is used to generate code from a model that contain a package with subpackages ? thanks Sara > Hey sara, > > that are the meta-annotations that META uses to build des metamodel > for the classes. See for example FAMIXMethod, or any other famix > class, to learn how this is used. > > Also you may find some slides on my website > > http://www.iam.unibe.ch/~akuhn/Documents/Slides/2006-Moose- > GoingMeta.pdf > > cheers, > AA > > On 21 May 2007, at 14:28 , sellossa(a)ensieta.fr wrote: > >> hi! >> >> I am still working on the code generator in Moose. >> With the BasicCodeGenerator class, you generate a metamodelling >> protocol >> for each attribute of a EMOF class >> What is the use of these "metamodel methods" ? >> >> thanks >> >> Sara >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply

6182

days inactive

6183

days old

moose-dev@list.inf.unibe.ch

Manage subscription

6 comments

2 participants

tags (0)

participants (2)

Adrian Kuhn
sellossa＠ensieta.fr