Hi!
Sorry, I did not carefully see parentPackage and parentScope. Nevermind.
Cheers, Alexandre
On 2 Oct 2011, at 03:36, Tudor Girba wrote:
Hi Alex,
I think I do not understand your mail :).
mooseName should be a fully qualified unique name as often as possible. It is definitely intended to be used like you mentioned in your mail (e.g., using entityNamed:).
So, where do you see mooseName returning the name only?
Cheers, Doru
On 1 Oct 2011, at 18:19, Alexandre Bergel wrote:
Hi!
[context: I am reviving CAnalyzer. My goal is to have it part of Moose for good. ]
At the time I worked on it, we had mooseName that return the fully qualified name (e.g., 'file2.hunit.recGlobal'). This was quite handy to lookup value. For example, I could write:
mooseModel entityNamed: 'file2.hunit.recGlobal'
this will return the definition of recGlobal defined in the file2.h.
Apparently, mooseName now returns the name (a String) as a symbol. The method printOn: return the fully qualified name.
We had some discussion some times ago, but I kind of forgot what the motivation was for that change. Should't we have a way to fully quality entities?
Cheers, Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev