Re: [Confuse-devel] questions about libconfuse code / conditionalincludes...

[Josh Kropf]

Hi Wolfgang,

I'm not one of the confuse devs but I was just curious why you believe
libconfuse is not a standard library?

On the few systems I've used libconfuse is readily available in the package
management system (Debian apt, FreeBSD ports, Gentoo portage, Mac OSX
macports, etc)


On Mon, 18 Feb 2008 22:29:19 +0100, Wolfgang Dautermann
<address@hidden> wrote:
> Dear Libconfuse-team,
> I was searching for a config file parser code, to include in our (GPL)
> project. The libconfuse-code seems good for our purposes.
> 
> I have a few questions:
> (a) Including the files in GPL Software is okay (as far as I know) - as
> long as I leave the copyright-notice as it is?
> 
> (b) I want to include the source files directly in our project (because
> I believe, libconfuse is not a standard library...). I have modified the
> source, so that it compiles now within my project.
> 
> But why do you - for example - in confuse.c conditionally include
> <stdlib.h>:
> 
> #ifdef HAVE_STDLIB_H
> # include <stdlib.h>
> #endif
> 
> - and in lexer.c not? (and the same with other includes...)
> 
> The library will not compile on system with a missing stdlib.h (since it
> uses malloc() and that requires that include file). Right?
> These conditional includes makes it harder to include the files in other
> projects.
> 
> Of course I can remove that #ifdefs, but it would be easier, if I could
> include the unmodified files...
> 
> Best regards,
> Wolfgang
> 
> 
> 
> 
> 
> _______________________________________________
> Confuse-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/confuse-devel