Not directly in the thread of the discussion :
I can understand the fear of having very long name, but: - Abbreviation make it just a little bit more difficult to understand things - the Pharo/Moose/... universe is already full of a lot of names (each new project makes a point to add its contribution to the babel tower of names) to the point that I felt the need to create a dictionary to try to remember and understand what people where talking about.
In conclusion, I would suggest that people think a good deal before using any abbreviations, and also before introducing any new project name ...
nicolas
On Mon, Sep 27, 2010 at 6:16 PM, Lukas Renggli renggli@gmail.com wrote:
Please note that the MA* (with an uppercase $A) prefix is already taken by Magritte. Ma* (with a lowercase $a) is taken by Magma, if I remember correctly they renamed their classes at some point a long time ago to avoid the conflict with Magritte.
Lukas
On 27 September 2010 17:51, Simon Denier Simon.Denier@inria.fr wrote:
I just performed a mass class renaming in Moose Algos Graph. Some classes still had the old prefix MO*, they now all have a MA* prefix. Class references in default Moose have been updated too (this includes DSM...)
So, if you use Moose-Algos-Graph and your package is not part of Moose default, you might to take a look and see if you need to update some references.
Also, the API of MAGraphAlgorithm has been extracted into trait MATGraphBuilder if someone wants to reuse it in a different setting (as requested). I don't support nested graph for now though, as it is not clear for me the best way to build them.
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Lukas Renggli www.lukas-renggli.ch
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev