On Fri, Sep 30, 2011 at 12:35 AM, Brian Aker <br...@tangent.org> wrote:
> The java scheme, would be org.drizzle.... I don't know that we need to go
> that far.
We shouldn't go that far, we should assume that when I commit code to
my drizzle repository, it's mostly under org.drizzle implicitly. I
don't see a benefit of having "globally unique" namespaces like in
Java.
But we could copy another practice from Java: namespaces and class
names are identical to the directory and filenames where you find
them. This would mean:
If file is in
drizzled/*.cc => namespace drizzled {
drizzled/optimizer/*.cc => namespace drizzled { namespace optimizer { (*)
If file is in
plugin/plugin_name/*.cc => namespace plugin { namespace plugin_name {
etc...
*) This assumes breaking "drizzled" into sub-namespaces makes sense,
I don't know if it does. Maybe files in drizzled/optimizer actually
assume they are in drizzled namespace and use symbols based on that
assumption.
henrik
--
henrik.i...@avoinelama.fi
+358-40-8211286 skype: henrik.ingo irc: hingo
www.openlife.cc
My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : drizzle-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
