Hi Stepharo, Thanks for your interest in these issues. As I said I prepared a package where you can reproduce the three issues. http://www.list.inf.unibe.ch/pipermail/moose-dev/attachments/20160908/e2e31e... http://www.list.inf.unibe.ch/pipermail/moose-dev/attachments/20160908/e2e31e84/attachment.obj You may want to have a closer look. Enjoy, Michel.
Hi michel
Le 8/9/16 à 23:01, Michel Bany a écrit :
Hello Moose lovers,
At the request of Stéphane Ducasse, I am sending this email to the Moose developers mailing list.
While working on the VisualWorks importer I stumble on three issues that I am describing shortly below.
- An endless loop occurs during an MSE export when an entity’s property is not set.
can you describe your solution?
- It is very easy to create duplicate entities without noticing
- When entities are not correctly linked to the model, #allInstancesDo: is sent making the processing extremely slow.
Can you tell us exactly what was the problem with the sourceModel?
Since it is not an easy task to precisely describe the corresponding symptoms, I prepared a package where those three issues can be reproduced using SUnit tests. The package is attached. Read carefully the comments that I inserted in each test, before running it.
Enjoy,
Michel
Hi Michel,
Somehow the attachment did not come through. Could you try again? Or maybe send a link?
Cheers, Doru
On Oct 9, 2016, at 9:51 AM, Michel Bany michel.bany@gmail.com wrote:
Hi Stepharo, Thanks for your interest in these issues. As I said I prepared a package where you can reproduce the three issues. http://www.list.inf.unibe.ch/pipermail/moose-dev/attachments/20160908/e2e31e... You may want to have a closer look. Enjoy, Michel.
Hi michel
Le 8/9/16 à 23:01, Michel Bany a écrit :
Hello Moose lovers,
At the request of Stéphane Ducasse, I am sending this email to the
Moose developers mailing list.
While working on the VisualWorks importer I stumble on three issues
that I am describing shortly below.
- An endless loop occurs during an MSE export when an entity’s
property is not set.can you describe your solution?
- It is very easy to create duplicate entities without noticing
- When entities are not correctly linked to the model,
#allInstancesDo: is sent making the processing extremely slow.Can you tell us exactly what was the problem with the sourceModel?
Since it is not an easy task to precisely describe the corresponding
symptoms, I prepared a package where those three issues can be
reproduced using SUnit tests. The package is attached. Read carefully
the comments that I inserted in each test, before running it.
Enjoy,
Michel
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
-- www.tudorgirba.com www.feenk.com
“Live like you mean it."
Somehow the attachment did not come through. Could you try again? Or maybe send a link?
Hi Doru, There is a link in my previous emails. Once downloaded, the file extension should be replaced with .mcz The link is repeated below
http://www.list.inf.unibe.ch/pipermail/moose-dev/attachments/20160908/e2e31e...
Enjoy,
Michel
---------- Forwarded message ---------- From: *Michel Bany* michel.bany@gmail.com Date: Sunday, 9 October 2016 Subject: Re: [Moose-dev] Re: Three Moose issues To: moose-dev@list.inf.unibe.ch, stepharo@free.fr
Hi Stepharo,
Thanks for your interest in these issues.
As I said I prepared a package where you can reproduce the three issues.
http://www.list.inf.unibe.ch/pipermail/moose-dev/attachments/20160908/e2e31e...
You may want to have a closer look.
Enjoy,
Michel.
Hi michel
Le 8/9/16 à 23:01, Michel Bany a écrit :
- Hello Moose lovers,
*>>* At the request of Stéphane Ducasse, I am sending this email to the *>* Moose developers mailing list. *>>* While working on the VisualWorks importer I stumble on three issues *>* that I am describing shortly below. *>>* 1. An endless loop occurs during an MSE export when an entity’s *>* property is not set. *> can you describe your solution?
- It is very easy to create duplicate entities without noticing
*>* 2. When entities are not correctly linked to the model, *>* #allInstancesDo: is sent making the processing extremely slow. *> Can you tell us exactly what was the problem with the sourceModel?
- Since it is not an easy task to precisely describe the corresponding
*>* symptoms, I prepared a package where those three issues can be *>* reproduced using SUnit tests. The package is attached. Read carefully *>* the comments that I inserted in each test, before running it. *>>* Enjoy, *>>* Michel*
-
Michel Bany -
Tudor Girba