On Fri, Sep 30, 2011 at 12:19 PM, Henrik Ingo <[email protected]> wrote: > 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 {
plugin::<name> is good, but an extra namespace shouldn't be required if you create another sub dir. > 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. That's being done already. But IMO one can also have too many namespaces. -- Olaf _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
