Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-29 Thread Steven G. Johnson
Paul Eggert wrote: OK, thanks, I installed that, after tightening up the documentation a bit. Here's the documentation patch I installed. Great! A note in NEWS might be worthwhile as well.

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-28 Thread Paul Eggert
OK, thanks, I installed that, after tightening up the documentation a bit. Here's the documentation patch I installed. --- autoconf.texi.~1.1120~ 2006-12-28 22:17:02.0 -0800 +++ autoconf.texi 2006-12-28 22:40:28.0 -0800 @@ -8252,8 +8252,15 @@ output. @defmacx

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-27 Thread Steven G. Johnson
Paul Eggert wrote: Paul Eggert wrote: That could well be, but it was never documented and it's not clear to me what the semantics would be. Are arbitrary characters allowed in the macro name? Surely not. No, just things that are valid in cpp #defines. Surely that's too strong as well. Are

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-27 Thread Paul Eggert
Steven G. Johnson [EMAIL PROTECTED] writes: why not say that the characters must be in [A-Za-z0-9_,()], and must form a valid cpp identifier and (optionally) a valid cpp argument list? That's a reasonable restriction, except (Ellipses are a C99 feature and it would not be a good idea to

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-25 Thread Paul Eggert
Steven G. Johnson [EMAIL PROTECTED] writes: (In fact, I believe I'm the one who originally patched autoconf to support macro arguments in AC_DEFINE.) That could well be, but it was never documented and it's not clear to me what the semantics would be. Are arbitrary characters allowed in the

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-19 Thread Stepan Kasal
Hello, On Tue, Dec 19, 2006 at 01:15:17PM +0200, Andrey Simonenko wrote: For example macro with arguments, depending on configure tests its value can be different. In config.h.in there can be #undef DEF (written by hands or generated by autoheader) and configure can change this line to

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-19 Thread Ralf Wildenhues
* Stepan Kasal wrote on Tue, Dec 19, 2006 at 12:40:33PM CET: On Tue, Dec 19, 2006 at 01:15:17PM +0200, Andrey Simonenko wrote: For example macro with arguments, depending on configure tests its value can be different. In config.h.in there can be #undef DEF (written by hands or generated by

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-18 Thread Stepan Kasal
Hello, On Fri, Dec 15, 2006 at 10:35:37AM -0800, Paul Eggert wrote: Andrey Simonenko [EMAIL PROTECTED] writes: AC_DEFINE([DEF(x)], [somevalue]) Ouch! That's not supported, and I'm surprised you got it to work as well as it did. status.m4 contains a code which supports this, so until

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-18 Thread Stepan Kasal
Hello Andrey, On Mon, Dec 18, 2006 at 03:40:08PM +0200, Andrey Simonenko wrote: AC_DEFINE([DEF(x)], [somevalue], [A macro to do a woo.]) As I understand this trick will not be supported in next versions of autoconf, so I reorganize logic of my .h files and now only

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-18 Thread Ralf Wildenhues
* Stepan Kasal wrote on Mon, Dec 18, 2006 at 07:31:59PM CET: I understand that there is no real reason to use this feature, but OTOH, when we remove it we'll again hear cries that the Autotools people are never able to produce a backward compatible release. Shouldn't we rather maintain the

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-18 Thread Paul Eggert
AC_DEFINE([DEF(x)], [somevalue]) Ouch! That's not supported, and I'm surprised you got it to work as well as it did. status.m4 contains a code which supports this, so until now I had no idea that this may be deprecated. I think this feature was available since the beginning of

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-15 Thread Stepan Kasal
[ This is part 1 of 2 of my answer to the report. ] Hello, On Thu, Dec 14, 2006 at 02:32:54PM +0200, Andrey Simonenko wrote: There is something different between 2.59 and 2.61 versions, indeed, you have discovered a regression, thank you. My reply comes in two mails; this one explains the

AC_CONFIG_HEADERS regression (was: Re: autoconf 2.61: AC_DEFINE variable with parenthesis)

2006-12-15 Thread Stepan Kasal
[ This is part 2 of 2 of my answer to the report. ] Hello, On Thu, Dec 14, 2006 at 02:32:54PM +0200, Andrey Simonenko reported the following regression: The temmplate: config.h.in: # define ABC # define DEF(x) results in: [...] autoconf-2.59: /* config.h. Generated by configure. */ #

Re: autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-15 Thread Paul Eggert
Andrey Simonenko [EMAIL PROTECTED] writes: AC_DEFINE([DEF(x)], [somevalue]) Ouch! That's not supported, and I'm surprised you got it to work as well as it did. First things first: we have to clarify the documentation to make it clearer that this isn't supposed to work, and add a warning in

autoconf 2.61: AC_DEFINE variable with parenthesis

2006-12-14 Thread Andrey Simonenko
Hello, There is something different between 2.59 and 2.61 versions, which does not allow to AC_DEFINE variable with parenthesis in the same way as in 2.59. Environment: FreeBSD, perl-5.8.8, m4-1.4.8, autoconf-2.61. configure.ac: AC_INIT([TEST], [1], [somebody]) AC_DEFINE([ABC], [something])