[Moose-dev] removing the mooseName caching mechanism

Hi, A while ago we put in place a caching mechanism for mooseName. While this has an impact on performance, it makes it a pain to play with the model in any sort of dynamic fashion. It also makes debugging very difficult especially during the development of new importers. Furthermore, it also has issues with assumptions about creating global caches at the model level which are not correct: FAMIXNamedEntities are not uniquely named in the whole model, they are uniquely named within their own type, and for that we already have a cache in the groups. For example, "model allClasses” will give us a group that will also have a cache by the mooseName of classes. This is a heads up that I want to remove this feature. Of course, we can still discuss about it. Cheers, Doru -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."