Vijay Samuel (GSOC): vjsamuel
Looking deeper and deeper into the drizzleslap.cc and learning boost::program_options I was able to come up with more and more solutions to remove the custom code from slap. I have completely removed my_long_options[] from slap(which will be a pleasing sight to most of the people working on drizzle after the branch gets merged I guess ). The changes that I intend to bring into slap within the next couple of days are as follows:
1. Bring program_options::options_description into main() instead of having it global(my initial assumption was that po::options_description would be used by several functions. I proved to myself that this assumption is wrong. ) .
2. Refactor the get_options() function to accept variable_map from boost::program_options as a parameter instead of the command line and query the variable_map for the values of **value. This way, the handle_options() can be safely removed from slap.
It is important that the get_options() is called from main() only after the variable_map is built and the command line has been parsed, otherwise it would make no sense.
If all this is right then I’ ll be able to refactor slap completely in the next 1 and a half days and submit my branch.
URL: http://vjsamuel.wordpress.com/2010/05/11/changes-to-be-applied-in-the-near-future/
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
