RE: Questions: ./config.h.in & ./windows-NT/config.h.in

[Conrad T. Pino]

Hi Derek,

> From: Derek Robert Price
> 
> Actually, it shouldn't really matter.  I was thinking at first that,
> aesthetically, it might be more pleasing to generate a file with the
> version info and then use it in conjunction with the other source file
> to generate config.h with the perl script, but, pratically and upon
> further consideration, I think it probably makes more sense to leave
> the config.h.in ->config.h step where it is since that step can run
> without Perl and running the Perl script will need to be disabled
> unless --enable-maintainer-mode.

The drift between respective "config.h.in" is substantial.  A Perl
script implementation looks feasible.  The challenge lies in an in
depth analysis of element in "windows-NT/config.h.in" that don't
occur in "./config.h.in" which may require a larger chunk of time
than I have right now.  I plan to revisit this topic after finishing
the missing function prototype list I took up in early April 2004.

> Derek

Conrad