On Wed, Jun 29, 2011 at 10:57 PM, Olaf van der Spek <[email protected]> wrote: > On Wed, Jun 29, 2011 at 9:55 PM, Henrik Ingo <[email protected]> > wrote: >> I don't know exactly what you are doing / talking about here, but... > > It's for reading defaults (host, port, socket, user, pass, database) > from conf files. > >> In MySQL at least, client and server and all utilities use the same >> ini file. That has always worked well. >> >> If drizzled uses boost to parse its ini file, then why can't >> libdrizzle too? Otoh if someone writes a parser for libdrizzle, why >> wouldn't drizzled use that code too? > > A dependency on Boost appears to be unwanted for the client lib.
I don't get why. Still the question remains - if Boost is unwanted for the client, what additional benefit does the parser provide to drizzled. It would make more sense that all components use one and the same parser to read the same config file. (Ie, if client can't use Boost, then drizzled should use the home grown one.) henrik -- [email protected] +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 : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
