On Mon, 8 Mar 2010, Ralf Corsepius wrote:
IMHO, the only real reason to rename configure.in to configure.ac is, that
some future Autoconf version may cease to accept the 'bugward' compatible
old name.
Only partially.
Suffix rules/mime-types are the keywords you are looking for. Whether the
files are named *.ac or *.in doesn't make much of a difference to autoconf,
but to other tools, e.g. automake, GUIs, browsers, editors etc.
agreed, except for automake which still accepts both configure.in or
configure.ac (but that also may change with future versions).
Everything else is philosophy/ideology.
Well, I presume your C-sources are named *.jpg?
Certainly not, and I sincerely hope this was meant as joke!
Regards
Peter
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
