Hi Henrik,
On 29/06/11 23:02, Henrik Ingo wrote:
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:
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.)
For a client library we want as little dependencies as possible. In
fact I 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.
Drizzle client apps should and will use the Boost .ini parser.
Kind Regards
--
Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
