[Moose-dev] Re: Class renaming in Moose Algos Graph

On 28 sept. 2010, at 09:11, Tudor Girba wrote: > Hi Simon, > > It looks like while renaming you missed to publish some packages: MOTarjanNodeDSM still seems to inherit from the old MOTarjanNode, and because of that the build breaks :). Argh, never thought I could still be bitten by the non-dirty package bug in MC :( So changing a superclass does not make a package dirty mmm... I guess I will to check with Package Blueprints what's the impact of renaming classes. As for the prefix, I will take Mal, just because fireflies do not bite (...) > > Cheers, > Doru > > > On 27 Sep 2010, at 22:00, Tudor Girba wrote: > >> Hi Simon, >> >> These classes should be called MAlgo (or MAL ?). I started to do that a while ago, but apparently I forgot to commit this change. >> >> Cheers, >> Doru >> >> >> On 27 Sep 2010, at 19:42, Simon Denier wrote: >> >>> >>> On 27 sept. 2010, at 18:17, Lukas Renggli 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. >>> >>> >>> ok, one issue is that all classes in Moose-Algos (not only Moose-Algos-Graph) are prefixed with MA so we will need to change that... >>> >>> but at least now there is some consistency in class names. >>> >>> >>>> >>>> Lukas >>>> >>>> On 27 September 2010 17:51, Simon Denier <Simon.Denier(a)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(a)iam.unibe.ch >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>>> >>>> _______________________________________________ >>>> 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 >> >> -- >> www.tudorgirba.com >> >> "Not knowing how to do something is not an argument for how it cannot be done." >> > > -- > www.tudorgirba.com > > "Be rather willing to give than demanding to get." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- Simon