On Thu, Jun 30, 2011 at 12:20 AM, Andrew Hutchings <[email protected]> wrote: >> 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.) > > For a client library we want as little dependencies as possible. In fact I
Why? Most apps should use pre-packaged libs, in which case this compile-time dependency isn't a problem. > can't see why a library will need a .ini file. In my opinion the client app > should have the .ini parser and use function/method calls to setup the > library. To read drizzle.conf / mysql.conf for defaults (host, port, socket, user, pass, database). -- 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
