On Tue, 10 Jan 2006 12:42:29 -0800 Paul Eggert <eggert@xxxxxxxxxxx> wrote: PE> Vadim Zeitlin <vadim@xxxxxxxxxxxx> writes: PE> PE> > fact it's detected by an automatic precommit check in the project I'm PE> > working on PE> PE> Well, to solve your immediate problem, it ought to be easy enough to PE> exempt HAVE__* names from the precommit check. The precommit check PE> ought to be your servant, not your master. Yes, finally we're going to just work around this issue for now. So the discussion is a bit theoretical but still: PE> > Maybe the most logical would be to have AC_CXX_CHECK_FUNCS then? PE> PE> Can you use AC_LANG(C++) followed by AC_CHECK_FUNCS? I proposed AC_CXX_CHECK_FUNCS to avoid breaking compatibility. I.e. if some existing code used AC_CHECK_FUNCS(_foo) before (possibly after AC_LANG(C++)), then changing it to define HAVE_UNDERSCORE_FOO instead of HAVE__FOO would almost surely break it. While AC_CXX_CHECK_FUNCS wouldn't have had this problem. But it's true that logically AC_CHECK_FUNCS() shouldn't use identifiers with 2 underscores if the current language is C++. Regards, VZ _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
