Hi Monty, Looks good! One suggestion I would have is to integrate this into a top-level plugin object. So, instead of defining new globals in each plugin, be able to extend a base plugin class (not to be confused with the specific plugin class types like StorageEngine/UDFs/...). The variables could then be members of this plugin class, and we can store other things in this class as well (like module dependencies, configuration vars, ...). I'm just not a fan of introducing new globals when they could be encapsulated by a core plugin class type. The namespace prefix could also be defined in this class that will be used for sysvars and future config.
I'll have my thoughts more organized and some examples later, but just wanted to toss this out there. -Eric On Thu, Jul 02, 2009 at 04:19:20PM -0700, Monty Taylor wrote: > http://drizzle.org/wiki/Refactor_system_variables > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
