Status: New Owner: ---- Labels: Type-Defect Priority-Medium
New issue 562 by alexandr...@gmail.com: MooseElement should be removed http://code.google.com/p/moose-technology/issues/detail?id=562
It is legacy code.
Comment #1 on issue 562 by tu...@tudorgirba.com: MooseElement should be removed http://code.google.com/p/moose-technology/issues/detail?id=562
Indeed, it should be merged with MooseEntity.
Updates: Status: Started
Comment #2 on issue 562 by jannik.l...@gmail.com: MooseElement should be removed http://code.google.com/p/moose-technology/issues/detail?id=562
The two classes are merged. I removed MooseElement from the hierarchy in Moose. But I keep it, with a deprecated message in the method new.
We have to remove it for the release.
Updates: Owner: jannik.l...@gmail.com Cc: tudor.gi...@gmail.com Labels: Component-MooseCore Milestone-4.6
Comment #3 on issue 562 by tudor.gi...@gmail.com: MooseElement should be removed http://code.google.com/p/moose-technology/issues/detail?id=562
Good work.
I removed MooseElement. There is no class that depends on it.
Updates: Status: Fixed
Comment #4 on issue 562 by tudor.gi...@gmail.com: MooseElement should be removed http://code.google.com/p/moose-technology/issues/detail?id=562
Also, I just needed to merge the tests as well (always double check if there is no other commit before committing your changes:))
Excellent!
Alexandre
Le 23 sept. 2011 à 11:24, moose-technology@googlecode.com a écrit :
Updates: Owner: jannik.l...@gmail.com Cc: tudor.gi...@gmail.com Labels: Component-MooseCore Milestone-4.6
Comment #3 on issue 562 by tudor.gi...@gmail.com: MooseElement should be removed http://code.google.com/p/moose-technology/issues/detail?id=562
Good work.
I removed MooseElement. There is no class that depends on it.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
moose-technology＠googlecode.com