27 Nov
2009
27 Nov
'09
9:38 p.m.
Hi Stef,
If you are sure it did not change, than just use the baseline already
present.
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
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
--
www.tudorgirba.com
"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."
Cheers,
Doru
On 27 Nov 2009, at 21:09, Simon Denier wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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:
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Begin forwarded message:
> From: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Date: November 27, 2009 8:25:02 PM GMT+01:00
> To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr>
> Subject: [Pharo-project] new version of CAnalyzer?
> Reply-To: Pharo-project(a)lists.gforge.inria.fr
>
> hi alex
>
> did you publish a new version of the configurationOfCanalyzer?
>
> Stef
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-
> project
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev