Hi
I'm looking for a good name which covers both package and namespace concepts. 'ScopingEntity' sounds a bit too verbose. The reason is that today, we have queries like clientClassesOutOfMyPackage, clientClassesOutOfMyNamespace. There are strong similarities between such queries so that it can actually be written once and reused multiple times. Tomorrow, I want such queries to be defined in a trait and injected in both FamixPackage and FamixNamespace. But, I want a single good name to name both Namespace and Package. Container? -- Simon _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
> I'm looking for a good name which covers both package and namespace concepts. 'ScopingEntity' sounds a bit too verbose.
> > The reason is that today, we have queries like clientClassesOutOfMyPackage, clientClassesOutOfMyNamespace. There are strong similarities between such queries so that it can actually be written once and reused multiple times. Tomorrow, I want such queries to be defined in a trait and injected in both FamixPackage and FamixNamespace. But, I want a single good name to name both Namespace and Package. Container? I thought about "Container" before reaching the end of your email Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Simon Denier-3
Container exists already, so that is not good.
How about Scoper? :) Doru On 19 Aug 2010, at 16:23, Simon Denier wrote: > Hi > > I'm looking for a good name which covers both package and namespace > concepts. 'ScopingEntity' sounds a bit too verbose. > > The reason is that today, we have queries like > clientClassesOutOfMyPackage, clientClassesOutOfMyNamespace. There > are strong similarities between such queries so that it can actually > be written once and reused multiple times. Tomorrow, I want such > queries to be defined in a trait and injected in both FamixPackage > and FamixNamespace. But, I want a single good name to name both > Namespace and Package. Container? > > > -- > Simon > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Presenting is storytelling." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
On 19 août 2010, at 16:34, Tudor Girba wrote: > Container exists already, so that is not good. How about Module? But it has other implications... > > How about Scoper? :) ergh :) well, perhaps it will win by default. > > Doru > > > On 19 Aug 2010, at 16:23, Simon Denier wrote: > >> Hi >> >> I'm looking for a good name which covers both package and namespace concepts. 'ScopingEntity' sounds a bit too verbose. >> >> The reason is that today, we have queries like clientClassesOutOfMyPackage, clientClassesOutOfMyNamespace. There are strong similarities between such queries so that it can actually be written once and reused multiple times. Tomorrow, I want such queries to be defined in a trait and injected in both FamixPackage and FamixNamespace. But, I want a single good name to name both Namespace and Package. Container? >> >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "Presenting is storytelling." > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- Simon _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |