Begin forwarded message:
From: Stéphane Ducasse stephane.ducasse@inria.fr Date: November 27, 2009 8:25:02 PM GMT+01:00 To: Pharo Development Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] new version of CAnalyzer? Reply-To: Pharo-project@lists.gforge.inria.fr
hi alex
did you publish a new version of the configurationOfCanalyzer?
Stef
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Some people are a bit too hurried in this list :)
So...
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
(BTW, I am not sure about the best way to create a new version with metacello. Right now I copy-paste the previous version method (or the baseline) and perform the 'update package methods' operation - have to think of a better name).
It's neither perfect nor complete: for example we dont import local variables or parameters for now (which might be interested for type usage information). Also there is no guarantee that the importer deals with all possible ways of declaring a function or a variable or something else, because of the syntax of the xml data sources.
On 27 nov. 2009, at 16:46, Stéphane Ducasse wrote:
Begin forwarded message:
From: Stéphane Ducasse stephane.ducasse@inria.fr Date: November 27, 2009 8:25:02 PM GMT+01:00 To: Pharo Development Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] new version of CAnalyzer? Reply-To: Pharo-project@lists.gforge.inria.fr
hi alex
did you publish a new version of the configurationOfCanalyzer?
Stef
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
On Nov 27, 2009, at 9:09 PM, Simon Denier wrote:
Some people are a bit too hurried in this list :)
:)
So...
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
Why a 1.3 Did you change the architecture?
(BTW, I am not sure about the best way to create a new version with metacello. Right now I copy-paste the previous version method (or the baseline) and perform the 'update package methods' operation - have to think of a better name).
It's neither perfect nor complete: for example we dont import local variables or parameters for now (which might be interested for type usage information). Also there is no guarantee that the importer deals with all possible ways of declaring a function or a variable or something else, because of the syntax of the xml data sources.
Ok I will try
On 27 nov. 2009, at 16:46, Stéphane Ducasse wrote:
Begin forwarded message:
From: Stéphane Ducasse stephane.ducasse@inria.fr Date: November 27, 2009 8:25:02 PM GMT+01:00 To: Pharo Development Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] new version of CAnalyzer? Reply-To: Pharo-project@lists.gforge.inria.fr
hi alex
did you publish a new version of the configurationOfCanalyzer?
Stef
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 27 nov. 2009, at 17:16, Stéphane Ducasse wrote:
On Nov 27, 2009, at 9:09 PM, Simon Denier wrote:
Some people are a bit too hurried in this list :)
:)
So...
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
Why a 1.3 Did you change the architecture?
nope, it's still based on baseline 1.2, it's just a new version (btw, I dont see a diff between baseline 1.1 and 1.2)
(BTW, I am not sure about the best way to create a new version with metacello. Right now I copy-paste the previous version method (or the baseline) and perform the 'update package methods' operation - have to think of a better name).
It's neither perfect nor complete: for example we dont import local variables or parameters for now (which might be interested for type usage information). Also there is no guarantee that the importer deals with all possible ways of declaring a function or a variable or something else, because of the syntax of the xml data sources.
Ok I will try
On 27 nov. 2009, at 16:46, Stéphane Ducasse wrote:
Begin forwarded message:
From: Stéphane Ducasse stephane.ducasse@inria.fr Date: November 27, 2009 8:25:02 PM GMT+01:00 To: Pharo Development Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] new version of CAnalyzer? Reply-To: Pharo-project@lists.gforge.inria.fr
hi alex
did you publish a new version of the configurationOfCanalyzer?
Stef
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- 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
-- Simon
On Nov 27, 2009, at 9:29 PM, Simon Denier wrote:
On 27 nov. 2009, at 17:16, Stéphane Ducasse wrote:
On Nov 27, 2009, at 9:09 PM, Simon Denier wrote:
Some people are a bit too hurried in this list :)
:)
So...
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
Why a 1.3 Did you change the architecture?
nope, it's still based on baseline 1.2, it's just a new version (btw, I dont see a diff between baseline 1.1 and 1.2)
strange because it changes rio -> filesystem?
(BTW, I am not sure about the best way to create a new version with metacello. Right now I copy-paste the previous version method (or the baseline) and perform the 'update package methods' operation - have to think of a better name).
It's neither perfect nor complete: for example we dont import local variables or parameters for now (which might be interested for type usage information). Also there is no guarantee that the importer deals with all possible ways of declaring a function or a variable or something else, because of the syntax of the xml data sources.
Ok I will try
On 27 nov. 2009, at 16:46, Stéphane Ducasse wrote:
Begin forwarded message:
From: Stéphane Ducasse stephane.ducasse@inria.fr Date: November 27, 2009 8:25:02 PM GMT+01:00 To: Pharo Development Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] new version of CAnalyzer? Reply-To: Pharo-project@lists.gforge.inria.fr
hi alex
did you publish a new version of the configurationOfCanalyzer?
Stef
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- 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
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 27 nov. 2009, at 17:39, Stéphane Ducasse wrote:
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
Why a 1.3 Did you change the architecture?
nope, it's still based on baseline 1.2, it's just a new version (btw, I dont see a diff between baseline 1.1 and 1.2)
strange because it changes rio -> filesystem?
ah yes, I overlooked that.
-- Simon
That sounds great!
For Metacello release, I have the following process: - copy the current default into a new method called baselineXXX - change the annotation to be 'VERSION.MINORVERSION-baseline' - select the Configuration class in OBSystemBrowser, and invoke "Spawn New Version"
Cheers, Doru
On 27 Nov 2009, at 21:09, Simon Denier wrote:
Some people are a bit too hurried in this list :)
So...
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
(BTW, I am not sure about the best way to create a new version with metacello. Right now I copy-paste the previous version method (or the baseline) and perform the 'update package methods' operation - have to think of a better name).
It's neither perfect nor complete: for example we dont import local variables or parameters for now (which might be interested for type usage information). Also there is no guarantee that the importer deals with all possible ways of declaring a function or a variable or something else, because of the syntax of the xml data sources.
On 27 nov. 2009, at 16:46, Stéphane Ducasse wrote:
Begin forwarded message:
From: Stéphane Ducasse stephane.ducasse@inria.fr Date: November 27, 2009 8:25:02 PM GMT+01:00 To: Pharo Development Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] new version of CAnalyzer? Reply-To: Pharo-project@lists.gforge.inria.fr
hi alex
did you publish a new version of the configurationOfCanalyzer?
Stef
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Sometimes the best solution is not the best solution."
On Nov 27, 2009, at 9:23 PM, Tudor Girba wrote:
That sounds great!
For Metacello release, I have the following process:
- copy the current default into a new method called baselineXXX
but normally the baseline should rarely changes so I do not get it.
- change the annotation to be 'VERSION.MINORVERSION-baseline'
- select the Configuration class in OBSystemBrowser, and invoke "Spawn New Version"
what does it generate a new version with the versions number?
Stef
Cheers, Doru
On 27 Nov 2009, at 21:09, Simon Denier wrote:
Some people are a bit too hurried in this list :)
So...
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
(BTW, I am not sure about the best way to create a new version with metacello. Right now I copy-paste the previous version method (or the baseline) and perform the 'update package methods' operation - have to think of a better name).
It's neither perfect nor complete: for example we dont import local variables or parameters for now (which might be interested for type usage information). Also there is no guarantee that the importer deals with all possible ways of declaring a function or a variable or something else, because of the syntax of the xml data sources.
On 27 nov. 2009, at 16:46, Stéphane Ducasse wrote:
Begin forwarded message:
From: Stéphane Ducasse stephane.ducasse@inria.fr Date: November 27, 2009 8:25:02 PM GMT+01:00 To: Pharo Development Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] new version of CAnalyzer? Reply-To: Pharo-project@lists.gforge.inria.fr
hi alex
did you publish a new version of the configurationOfCanalyzer?
Stef
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Sometimes the best solution is not the best solution."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Stef,
That sounds great!
For Metacello release, I have the following process:
- copy the current default into a new method called baselineXXX
but normally the baseline should rarely changes so I do not get it.
If you are sure it did not change, than just use the baseline already present.
- change the annotation to be 'VERSION.MINORVERSION-baseline'
- select the Configuration class in OBSystemBrowser, and invoke
"Spawn New Version"
what does it generate a new version with the versions number?
Yes. It will ask for the baseline to read from and then it will generate a new method with hardcoded Monticello version numbers.
Cheers, Doru
Stef
Cheers, Doru
On 27 Nov 2009, at 21:09, Simon Denier wrote:
Some people are a bit too hurried in this list :)
So...
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
(BTW, I am not sure about the best way to create a new version with metacello. Right now I copy-paste the previous version method (or the baseline) and perform the 'update package methods' operation - have to think of a better name).
It's neither perfect nor complete: for example we dont import local variables or parameters for now (which might be interested for type usage information). Also there is no guarantee that the importer deals with all possible ways of declaring a function or a variable or something else, because of the syntax of the xml data sources.
On 27 nov. 2009, at 16:46, Stéphane Ducasse wrote:
Begin forwarded message:
From: Stéphane Ducasse stephane.ducasse@inria.fr Date: November 27, 2009 8:25:02 PM GMT+01:00 To: Pharo Development Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] new version of CAnalyzer? Reply-To: Pharo-project@lists.gforge.inria.fr
hi alex
did you publish a new version of the configurationOfCanalyzer?
Stef
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Sometimes the best solution is not the best solution."
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
"Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."
Cool now I do not understand why self loadVersion: '1.3' does not load anything. Simon did you try it?
Stef
On Nov 27, 2009, at 9:38 PM, Tudor Girba wrote:
Hi Stef,
That sounds great!
For Metacello release, I have the following process:
- copy the current default into a new method called baselineXXX
but normally the baseline should rarely changes so I do not get it.
If you are sure it did not change, than just use the baseline already present.
- change the annotation to be 'VERSION.MINORVERSION-baseline'
- select the Configuration class in OBSystemBrowser, and invoke "Spawn New Version"
what does it generate a new version with the versions number?
Yes. It will ask for the baseline to read from and then it will generate a new method with hardcoded Monticello version numbers.
Cheers, Doru
Stef
Cheers, Doru
On 27 Nov 2009, at 21:09, Simon Denier wrote:
Some people are a bit too hurried in this list :)
So...
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
(BTW, I am not sure about the best way to create a new version with metacello. Right now I copy-paste the previous version method (or the baseline) and perform the 'update package methods' operation - have to think of a better name).
It's neither perfect nor complete: for example we dont import local variables or parameters for now (which might be interested for type usage information). Also there is no guarantee that the importer deals with all possible ways of declaring a function or a variable or something else, because of the syntax of the xml data sources.
On 27 nov. 2009, at 16:46, Stéphane Ducasse wrote:
Begin forwarded message:
From: Stéphane Ducasse stephane.ducasse@inria.fr Date: November 27, 2009 8:25:02 PM GMT+01:00 To: Pharo Development Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] new version of CAnalyzer? Reply-To: Pharo-project@lists.gforge.inria.fr
hi alex
did you publish a new version of the configurationOfCanalyzer?
Stef
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Sometimes the best solution is not the best solution."
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
"Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 27 nov. 2009, at 17:44, Stéphane Ducasse wrote:
Cool now I do not understand why self loadVersion: '1.3' does not load anything. Simon did you try it?
yes it works in my image. Be sure to start from a recent Moose version also (ConfigurationOfMoose updateDefault from a beta2).
Stef
On Nov 27, 2009, at 9:38 PM, Tudor Girba wrote:
Hi Stef,
That sounds great!
For Metacello release, I have the following process:
- copy the current default into a new method called baselineXXX
but normally the baseline should rarely changes so I do not get it.
If you are sure it did not change, than just use the baseline already present.
- change the annotation to be 'VERSION.MINORVERSION-baseline'
- select the Configuration class in OBSystemBrowser, and invoke
"Spawn New Version"
what does it generate a new version with the versions number?
Yes. It will ask for the baseline to read from and then it will generate a new method with hardcoded Monticello version numbers.
Cheers, Doru
Stef
Cheers, Doru
On 27 Nov 2009, at 21:09, Simon Denier wrote:
Some people are a bit too hurried in this list :)
So...
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
(BTW, I am not sure about the best way to create a new version with metacello. Right now I copy-paste the previous version method (or the baseline) and perform the 'update package methods' operation - have to think of a better name).
It's neither perfect nor complete: for example we dont import local variables or parameters for now (which might be interested for type usage information). Also there is no guarantee that the importer deals with all possible ways of declaring a function or a variable or something else, because of the syntax of the xml data sources.
On 27 nov. 2009, at 16:46, Stéphane Ducasse wrote:
Begin forwarded message:
> From: Stéphane Ducasse stephane.ducasse@inria.fr > Date: November 27, 2009 8:25:02 PM GMT+01:00 > To: Pharo Development Pharo-project@lists.gforge.inria.fr > Subject: [Pharo-project] new version of CAnalyzer? > Reply-To: Pharo-project@lists.gforge.inria.fr > > hi alex > > did you publish a new version of the configurationOfCanalyzer? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Sometimes the best solution is not the best solution."
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
"Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."
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
-- Simon
On 27 nov. 2009, at 17:23, Tudor Girba wrote:
That sounds great!
For Metacello release, I have the following process:
- copy the current default into a new method called baselineXXX
- change the annotation to be 'VERSION.MINORVERSION-baseline'
- select the Configuration class in OBSystemBrowser, and invoke
"Spawn New Version"
Ah yes, I was looking at an old description of the tools and overshot this choice.
Cheers, Doru
On 27 Nov 2009, at 21:09, Simon Denier wrote:
Some people are a bit too hurried in this list :)
So...
After a week of work and discussion, we (Alex and I) are pleased to announce that the metamodel for C looks good enough to perform some analysis.
See the tests in CAnalyzerTest:test famix integration for some specifications of CA entities.
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
(BTW, I am not sure about the best way to create a new version with metacello. Right now I copy-paste the previous version method (or the baseline) and perform the 'update package methods' operation - have to think of a better name).
It's neither perfect nor complete: for example we dont import local variables or parameters for now (which might be interested for type usage information). Also there is no guarantee that the importer deals with all possible ways of declaring a function or a variable or something else, because of the syntax of the xml data sources.
On 27 nov. 2009, at 16:46, Stéphane Ducasse wrote:
Begin forwarded message:
From: Stéphane Ducasse stephane.ducasse@inria.fr Date: November 27, 2009 8:25:02 PM GMT+01:00 To: Pharo Development Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] new version of CAnalyzer? Reply-To: Pharo-project@lists.gforge.inria.fr
hi alex
did you publish a new version of the configurationOfCanalyzer?
Stef
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Sometimes the best solution is not the best solution."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
I also updated the Configuration so ConfigurationOfCAnalyzer loadVersion: '1.3' should load a working analyzer.
I updated the version 1.3 of ConfigurationOfCAnalyzer. It now uses the last version of XML-Parser and Pastell. I fixed some brocken tests in these packages (without touching the base code however).
Cheers, Alexandre
-
Alexandre Bergel -
Simon Denier -
Stéphane Ducasse -
Tudor Girba