Hi, how can i get the invoked methods into the try{...}/catch{...} ? and LOC, attributes, etc... from those codes
thanks!
what do you want? Write exception in Smalltalk? for exceptions read : https://gforge.inria.fr/frs/download.php/26600/PBE2-Exceptions-2010-03-02.pd...
in a nutshell
try {}catch{}
=> [self doThat] on: Error do: [:exception | self doWhatheverYouwantwith: exception]
On Aug 31, 2010, at 7:08 PM, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ?
in moose you have to query the try catch browse a simple model with a try catch to see how this is extracted.
and LOC, attributes, etc... from those codes
thanks!
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
The thing is that i don't know how to obtain the information inside the try and the catch. Then, i would like to know if that is possible and how to do it.
Finally, in Pharo using Moose (Mondrian), draw that information and relationships.
Is in the context of a course on Software Quality and Assessment with Alexandre Bergel.
thanks! El mié, 01-09-2010 a las 12:03 +0200, Stéphane Ducasse escribió:
what do you want? Write exception in Smalltalk? for exceptions read : https://gforge.inria.fr/frs/download.php/26600/PBE2-Exceptions-2010-03-02.pd...
in a nutshell
try {}catch{}
=> [self doThat] on: Error do: [:exception | self doWhatheverYouwantwith: exception]
On Aug 31, 2010, at 7:08 PM, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ?
in moose you have to query the try catch browse a simple model with a try catch to see how this is extracted.
and LOC, attributes, etc... from those codes
thanks!
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 31 août 2010, at 19:08, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ? and LOC, attributes, etc... from those codes
Hi Felipe
For now, with a Java model imported with inFusion, you can get the list of exceptions caught/thrown in a method, but I don't think you get the java block structure of "try/catch". It would be pretty easy to add such a FAMIX.JavaBlock entity (not to be confused with a Smalltalk block) and define metric/query on this class.
But first, some Java importer needs to handle this case.
It helps to understand your problem if you give more information about your goal. So, what you are trying to do?
-- Simon
I have been used that information what you said. For that reason i would like to do that as mentionated.
thanks! El mié, 01-09-2010 a las 15:22 +0200, Simon Denier escribió:
On 31 août 2010, at 19:08, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ? and LOC, attributes, etc... from those codes
Hi Felipe
For now, with a Java model imported with inFusion, you can get the list of exceptions caught/thrown in a method, but I don't think you get the java block structure of "try/catch". It would be pretty easy to add such a FAMIX.JavaBlock entity (not to be confused with a Smalltalk block) and define metric/query on this class.
But first, some Java importer needs to handle this case.
It helps to understand your problem if you give more information about your goal. So, what you are trying to do?
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Meanwhile i'm waiting the response of the inFusion people.
thanks! El mié, 01-09-2010 a las 15:22 +0200, Simon Denier escribió:
On 31 août 2010, at 19:08, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ? and LOC, attributes, etc... from those codes
Hi Felipe
For now, with a Java model imported with inFusion, you can get the list of exceptions caught/thrown in a method, but I don't think you get the java block structure of "try/catch". It would be pretty easy to add such a FAMIX.JavaBlock entity (not to be confused with a Smalltalk block) and define metric/query on this class.
But first, some Java importer needs to handle this case.
It helps to understand your problem if you give more information about your goal. So, what you are trying to do?
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
Like Simon said, this information is available neither in FAMIX nor in the Java exporter. I am pretty sure that the parser produces the AST information, but I think that the MEMORIA meta-model (this is the meta- model of inFusion) does not capture this info. Let us know if you find something.
Perhaps another idea is to use an AST yourself, for example, produced by srcML, or by PetitJava.
Cheers, Doru
On 1 Sep 2010, at 19:41, Felipe Ignacio Valverde Campos wrote:
Meanwhile i'm waiting the response of the inFusion people.
thanks! El mié, 01-09-2010 a las 15:22 +0200, Simon Denier escribió:
On 31 août 2010, at 19:08, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ? and LOC, attributes, etc... from those codes
Hi Felipe
For now, with a Java model imported with inFusion, you can get the list of exceptions caught/thrown in a method, but I don't think you get the java block structure of "try/catch". It would be pretty easy to add such a FAMIX.JavaBlock entity (not to be confused with a Smalltalk block) and define metric/query on this class.
But first, some Java importer needs to handle this case.
It helps to understand your problem if you give more information about your goal. So, what you are trying to do?
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
or vervein.
Stef
On Sep 1, 2010, at 10:12 PM, Tudor Girba wrote:
Hi,
Like Simon said, this information is available neither in FAMIX nor in the Java exporter. I am pretty sure that the parser produces the AST information, but I think that the MEMORIA meta-model (this is the meta-model of inFusion) does not capture this info. Let us know if you find something.
Perhaps another idea is to use an AST yourself, for example, produced by srcML, or by PetitJava.
Cheers, Doru
On 1 Sep 2010, at 19:41, Felipe Ignacio Valverde Campos wrote:
Meanwhile i'm waiting the response of the inFusion people.
thanks! El mié, 01-09-2010 a las 15:22 +0200, Simon Denier escribió:
On 31 août 2010, at 19:08, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ? and LOC, attributes, etc... from those codes
Hi Felipe
For now, with a Java model imported with inFusion, you can get the list of exceptions caught/thrown in a method, but I don't think you get the java block structure of "try/catch". It would be pretty easy to add such a FAMIX.JavaBlock entity (not to be confused with a Smalltalk block) and define metric/query on this class.
But first, some Java importer needs to handle this case.
It helps to understand your problem if you give more information about your goal. So, what you are trying to do?
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yep,
there is a new Java to MSE exporter called Verveine
Can be found at: svn+ssh://<USERNAME>@scm.gforge.inria.fr/svn/lsehub/Projects/Verveine or: https://scm.gforge.inria.fr/svn/lse/Projects/Verveine
Currently it only generates: - packages entities (Namespace) - class entities - method - parameters - attributes - method invocation
But it is not very difficult to add new information if one understands AST visiting.
Verveine is based on JDT (batch). There is a shell script verveinej.sh in the root directory of the project to run it on a java directory
I can provide help to augment it although I don't have time now to do much on it (back to school next monday)
nicolas
On Wed, Sep 1, 2010 at 10:37 PM, Stéphane Ducasse stephane.ducasse@inria.fr wrote:
or vervein.
Stef
On Sep 1, 2010, at 10:12 PM, Tudor Girba wrote:
Hi,
Like Simon said, this information is available neither in FAMIX nor in the Java exporter. I am pretty sure that the parser produces the AST information, but I think that the MEMORIA meta-model (this is the meta-model of inFusion) does not capture this info. Let us know if you find something.
Perhaps another idea is to use an AST yourself, for example, produced by srcML, or by PetitJava.
Cheers, Doru
On 1 Sep 2010, at 19:41, Felipe Ignacio Valverde Campos wrote:
Meanwhile i'm waiting the response of the inFusion people.
thanks! El mié, 01-09-2010 a las 15:22 +0200, Simon Denier escribió:
On 31 août 2010, at 19:08, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ? and LOC, attributes, etc... from those codes
Hi Felipe
For now, with a Java model imported with inFusion, you can get the list of exceptions caught/thrown in a method, but I don't think you get the java block structure of "try/catch". It would be pretty easy to add such a FAMIX.JavaBlock entity (not to be confused with a Smalltalk block) and define metric/query on this class.
But first, some Java importer needs to handle this case.
It helps to understand your problem if you give more information about your goal. So, what you are trying to do?
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
That is nice indeed. Cyrille, would it be difficult to use this as a testbed for the JNIPort, given that you can control the Java code as well?
One idea would be to not have to go through MSE, but to directly read the from the Java objects.
Cheers, Doru
On 3 Sep 2010, at 11:04, Nicolas Anquetil wrote:
Yep,
there is a new Java to MSE exporter called Verveine
Can be found at: svn+ssh://<USERNAME>@scm.gforge.inria.fr/svn/lsehub/Projects/Verveine or: https://scm.gforge.inria.fr/svn/lse/Projects/Verveine
Currently it only generates:
- packages entities (Namespace)
- class entities
- method
- parameters
- attributes
- method invocation
But it is not very difficult to add new information if one understands AST visiting.
Verveine is based on JDT (batch). There is a shell script verveinej.sh in the root directory of the project to run it on a java directory
I can provide help to augment it although I don't have time now to do much on it (back to school next monday)
nicolas
On Wed, Sep 1, 2010 at 10:37 PM, Stéphane Ducasse stephane.ducasse@inria.fr wrote:
or vervein.
Stef
On Sep 1, 2010, at 10:12 PM, Tudor Girba wrote:
Hi,
Like Simon said, this information is available neither in FAMIX nor in the Java exporter. I am pretty sure that the parser produces the AST information, but I think that the MEMORIA meta- model (this is the meta-model of inFusion) does not capture this info. Let us know if you find something.
Perhaps another idea is to use an AST yourself, for example, produced by srcML, or by PetitJava.
Cheers, Doru
On 1 Sep 2010, at 19:41, Felipe Ignacio Valverde Campos wrote:
Meanwhile i'm waiting the response of the inFusion people.
thanks! El mié, 01-09-2010 a las 15:22 +0200, Simon Denier escribió:
On 31 août 2010, at 19:08, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/ catch{...} ? and LOC, attributes, etc... from those codes
Hi Felipe
For now, with a Java model imported with inFusion, you can get the list of exceptions caught/thrown in a method, but I don't think you get the java block structure of "try/catch". It would be pretty easy to add such a FAMIX.JavaBlock entity (not to be confused with a Smalltalk block) and define metric/query on this class.
But first, some Java importer needs to handle this case.
It helps to understand your problem if you give more information about your goal. So, what you are trying to do?
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Nicolas Anquetil Univ. Lille1 / INRIA-equipe RMod
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Don't give to get. Just give."
Yes it could be a good a test. Instead of generating FAMIXEntities in java and then exporting them as mse (that's what is doing Verveine currently), The idea would be to directly build our entities in the smalltalk image ?
2010/9/3 Tudor Girba tudor.girba@gmail.com
Hi,
That is nice indeed. Cyrille, would it be difficult to use this as a testbed for the JNIPort, given that you can control the Java code as well?
One idea would be to not have to go through MSE, but to directly read the from the Java objects.
Cheers, Doru
On 3 Sep 2010, at 11:04, Nicolas Anquetil wrote:
Yep,
there is a new Java to MSE exporter called Verveine
Can be found at: svn+ssh://<USERNAME>@scm.gforge.inria.fr/svn/lsehub/Projects/Verveine or: https://scm.gforge.inria.fr/svn/lse/Projects/Verveine
Currently it only generates:
- packages entities (Namespace)
- class entities
- method
- parameters
- attributes
- method invocation
But it is not very difficult to add new information if one understands AST visiting.
Verveine is based on JDT (batch). There is a shell script verveinej.sh in the root directory of the project to run it on a java directory
I can provide help to augment it although I don't have time now to do much on it (back to school next monday)
nicolas
On Wed, Sep 1, 2010 at 10:37 PM, Stéphane Ducasse stephane.ducasse@inria.fr wrote:
or vervein.
Stef
On Sep 1, 2010, at 10:12 PM, Tudor Girba wrote:
Hi,
Like Simon said, this information is available neither in FAMIX nor in the Java exporter. I am pretty sure that the parser produces the AST information, but I think that the MEMORIA meta-model (this is the meta-model of inFusion) does not capture this info. Let us know if you find something.
Perhaps another idea is to use an AST yourself, for example, produced by srcML, or by PetitJava.
Cheers, Doru
On 1 Sep 2010, at 19:41, Felipe Ignacio Valverde Campos wrote:
Meanwhile i'm waiting the response of the inFusion people.
thanks! El mié, 01-09-2010 a las 15:22 +0200, Simon Denier escribió:
On 31 août 2010, at 19:08, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ? > and LOC, attributes, etc... from those codes > >
Hi Felipe
For now, with a Java model imported with inFusion, you can get the list of exceptions caught/thrown in a method, but I don't think you get the java block structure of "try/catch". It would be pretty easy to add such a FAMIX.JavaBlock entity (not to be confused with a Smalltalk block) and define metric/query on this class.
But first, some Java importer needs to handle this case.
It helps to understand your problem if you give more information about your goal. So, what you are trying to do?
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Nicolas Anquetil Univ. Lille1 / INRIA-equipe RMod
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Don't give to get. Just give."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Exactly. Ideally, we would have the AST visitor directly in Smalltalk and create directly FAMIX objects to save memory. But, for starters, even a traversal of the corresponding FAMIX objects from the Java world would be just fine.
Doru
On 3 Sep 2010, at 11:26, Cyrille Delaunay wrote:
Yes it could be a good a test. Instead of generating FAMIXEntities in java and then exporting them as mse (that's what is doing Verveine currently), The idea would be to directly build our entities in the smalltalk image ?
2010/9/3 Tudor Girba tudor.girba@gmail.com Hi,
That is nice indeed. Cyrille, would it be difficult to use this as a testbed for the JNIPort, given that you can control the Java code as well?
One idea would be to not have to go through MSE, but to directly read the from the Java objects.
Cheers, Doru
On 3 Sep 2010, at 11:04, Nicolas Anquetil wrote:
Yep,
there is a new Java to MSE exporter called Verveine
Can be found at: svn+ssh://<USERNAME>@scm.gforge.inria.fr/svn/lsehub/Projects/Verveine or: https://scm.gforge.inria.fr/svn/lse/Projects/Verveine
Currently it only generates:
- packages entities (Namespace)
- class entities
- method
- parameters
- attributes
- method invocation
But it is not very difficult to add new information if one understands AST visiting.
Verveine is based on JDT (batch). There is a shell script verveinej.sh in the root directory of the project to run it on a java directory
I can provide help to augment it although I don't have time now to do much on it (back to school next monday)
nicolas
On Wed, Sep 1, 2010 at 10:37 PM, Stéphane Ducasse stephane.ducasse@inria.fr wrote: or vervein.
Stef
On Sep 1, 2010, at 10:12 PM, Tudor Girba wrote:
Hi,
Like Simon said, this information is available neither in FAMIX nor in the Java exporter. I am pretty sure that the parser produces the AST information, but I think that the MEMORIA meta-model (this is the meta-model of inFusion) does not capture this info. Let us know if you find something.
Perhaps another idea is to use an AST yourself, for example, produced by srcML, or by PetitJava.
Cheers, Doru
On 1 Sep 2010, at 19:41, Felipe Ignacio Valverde Campos wrote:
Meanwhile i'm waiting the response of the inFusion people.
thanks! El mié, 01-09-2010 a las 15:22 +0200, Simon Denier escribió:
On 31 août 2010, at 19:08, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ? and LOC, attributes, etc... from those codes
Hi Felipe
For now, with a Java model imported with inFusion, you can get the list of exceptions caught/thrown in a method, but I don't think you get the java block structure of "try/catch". It would be pretty easy to add such a FAMIX.JavaBlock entity (not to be confused with a Smalltalk block) and define metric/query on this class.
But first, some Java importer needs to handle this case.
It helps to understand your problem if you give more information about your goal. So, what you are trying to do?
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Nicolas Anquetil Univ. Lille1 / INRIA-equipe RMod
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Don't give to get. Just give."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Talking to Java from smalltalk is a plus for your cv
Cyrille
You see my subliminal messages :)
On Sep 3, 2010, at 11:26 AM, Cyrille Delaunay wrote:
Yes it could be a good a test. Instead of generating FAMIXEntities in java and then exporting them as mse (that's what is doing Verveine currently), The idea would be to directly build our entities in the smalltalk image ?
2010/9/3 Tudor Girba tudor.girba@gmail.com Hi,
That is nice indeed. Cyrille, would it be difficult to use this as a testbed for the JNIPort, given that you can control the Java code as well?
One idea would be to not have to go through MSE, but to directly read the from the Java objects.
Cheers, Doru
On 3 Sep 2010, at 11:04, Nicolas Anquetil wrote:
Yep,
there is a new Java to MSE exporter called Verveine
Can be found at: svn+ssh://<USERNAME>@scm.gforge.inria.fr/svn/lsehub/Projects/Verveine or: https://scm.gforge.inria.fr/svn/lse/Projects/Verveine
Currently it only generates:
- packages entities (Namespace)
- class entities
- method
- parameters
- attributes
- method invocation
But it is not very difficult to add new information if one understands AST visiting.
Verveine is based on JDT (batch). There is a shell script verveinej.sh in the root directory of the project to run it on a java directory
I can provide help to augment it although I don't have time now to do much on it (back to school next monday)
nicolas
On Wed, Sep 1, 2010 at 10:37 PM, Stéphane Ducasse stephane.ducasse@inria.fr wrote: or vervein.
Stef
On Sep 1, 2010, at 10:12 PM, Tudor Girba wrote:
Hi,
Like Simon said, this information is available neither in FAMIX nor in the Java exporter. I am pretty sure that the parser produces the AST information, but I think that the MEMORIA meta-model (this is the meta-model of inFusion) does not capture this info. Let us know if you find something.
Perhaps another idea is to use an AST yourself, for example, produced by srcML, or by PetitJava.
Cheers, Doru
On 1 Sep 2010, at 19:41, Felipe Ignacio Valverde Campos wrote:
Meanwhile i'm waiting the response of the inFusion people.
thanks! El mié, 01-09-2010 a las 15:22 +0200, Simon Denier escribió:
On 31 août 2010, at 19:08, Felipe Ignacio Valverde Campos wrote:
Hi, how can i get the invoked methods into the try{...}/catch{...} ? and LOC, attributes, etc... from those codes
Hi Felipe
For now, with a Java model imported with inFusion, you can get the list of exceptions caught/thrown in a method, but I don't think you get the java block structure of "try/catch". It would be pretty easy to add such a FAMIX.JavaBlock entity (not to be confused with a Smalltalk block) and define metric/query on this class.
But first, some Java importer needs to handle this case.
It helps to understand your problem if you give more information about your goal. So, what you are trying to do?
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Nicolas Anquetil Univ. Lille1 / INRIA-equipe RMod
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Don't give to get. Just give."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Cyrille Delaunay -
Felipe Ignacio Valverde Campos -
Nicolas Anquetil -
Simon Denier -
Stéphane Ducasse -
Tudor Girba