[EMAIL PROTECTED] (Steven M. Schweda) writes:
> #define VERSION_STRING "1.10-alpha1_sms1"
>
> Was there any reason to do this with a source module instead of a
> simple macro in a simple header file?
At some point that approach made it easy to read or change the
version, as the script "dist-wget" does. But I'm sure there are other
ways to do it, too.
> Was there any reason to use '#include <config.h>' instead of
> '#include "config.h"'?
Yes. The idea is that you can build in a separate directory and have
the compiler find the build directory's config.h instead of a config.h
previously configured in the source directory. Quoting Autoconf
manual:
Use `#include <config.h>' instead of `#include "config.h"', and
pass the C compiler a `-I.' option (or `-I..'; whichever directory
contains `config.h'). That way, even if the source directory is
configured itself (perhaps to make a distribution), other build
directories can also be configured without finding the `config.h'
from the source directory.
