Actually, I just realized that another better solution would be to *not* reimport implicitly and silently an existing output.mse file.
This features was created to allow incremental parsing, but when one wants to do so, one should specify an option to explicitly say so.
And the behaviour by default should be to ignore (erase) any pre-existing output.mse file.
nicolas
----- Mail original -----
> De:
[hidden email]
> À:
[hidden email]
> Envoyé: Mercredi 14 Décembre 2011 18:10:09
> Objet: [Moose-dev] Issue 762 in moose-technology: VerveineJ keeps the history of old entities, when invoked from the
> Moose interface
> Status: New
> Owner:
[hidden email]
> Labels: Type-Defect Priority-Medium
>
> New issue 762 by
[hidden email]: VerveineJ keeps the history of
> old
> entities, when invoked from the Moose interface
>
http://code.google.com/p/moose-technology/issues/detail?id=762>
> First, I invoke VerveineJ from Moose menu to analyse a program A. It
> analyses the program and imports its entities in a moose model. I
> invoke VJ
> once more from moose menu to analyse another program B. When VJ is
> executed
> and the entities of program B are imported, I also find in the same
> model
> the entities related to the program A. So, VerveineJ keeps the history
> of
> old entities, when invoked from Moose interface.
>
> I think the problem can be resolved by deleting output.mse once VJ has
> finished its analysis and the entities are imported in a moose model.
>
> _______________________________________________
> Moose-dev mailing list
>
[hidden email]
>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Locked
