Apologies for joining the conversation so late:
On 30 Jan 2007, at 07:23, Eric Blake wrote:
How about if M4 uses a slightly-different syntax, so that the two
uses
are never confused? That way, the conversion problem won't ever have
to be addressed, and Autoconf won't have to disable the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 1/30/2007 7:23 AM:
Let me think on this for a couple more days (as it is, I still haven't
completely implemented extended arguments in CVS m4; partly because I want
to do it right, so I want this thread to come to a
Eric Blake [EMAIL PROTECTED] writes:
+fatal need GNU m4 1.4.5 or later: $m4
+ unless system echo 'ifdef(mac,bug)dnl' | $m4 --trace=mac 21 | grep bug
/dev/null;
+
+# Detect if we can use feature added in M4 1.4.9 to warn user about $10.
+# Override the user's choice of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 2/8/2007 12:20 PM:
Can you please rewrite this so that it invokes m4 once instead of
twice, and doesn't use grep at all? You can use Perl's pattern
matching instead of grep. And I think you can test for both features
Eric Blake ebb9 at byu.net writes:
I tried your warnings now:
cat aclocal.m4 \EOF
AC_DEFUN([Y], [${1}])
define([Z], [${1}])
EOF
cat configure.ac \EOF
AC_INIT
AC_DEFUN([X], [${1}])
EOF
M4=m4\ --warn-syntax autoconf
| m4:aclocal.m4:1: Warning: semantics of `${1...}' in `Y'
Hello Eric,
Allow me to address specific points only, rather than the larger picture
of where to finally go.
* Eric Blake wrote on Tue, Jan 30, 2007 at 02:04:51PM CET:
According to Ralf Wildenhues on 1/29/2007 11:44 AM:
The Coding Style ends up being inconsistent with
$[#]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 1/31/2007 12:18 PM:
Hi Ralf, and thanks for the review,
Limiting to just one of your points:
I tried your warnings now:
cat aclocal.m4 \EOF
AC_DEFUN([Y], [${1}])
define([Z], [${1}])
EOF
cat configure.ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 1/29/2007 11:44 AM:
Hello Eric, all,
Hello in return,
* doc/autoconf.texi (Quoting and Parameters): New section.
This makes things inconsistent. Quoting `Coding Style':
| Otherwise, the closing bracket
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 1/29/2007 10:39 AM:
Eric Blake [EMAIL PROTECTED] writes:
Because I was hoping that M4 2.0 could borrow a leaf from shell parsing,
and ALSO implement things like ${1-default} that is more compact than the
current
Hello Eric, all,
* Eric Blake wrote on Sun, Jan 28, 2007 at 06:05:48AM CET:
* lib/m4sugar/m4sugar.m4: Cripple ${1} expansion in M4 2.0 for
portability with 1.4.x behavior.
* doc/autoconf.texi (Quoting and Parameters): New section.
(Quotation and Nested Macros): Touch
Eric Blake [EMAIL PROTECTED] writes:
Because I was hoping that M4 2.0 could borrow a leaf from shell parsing,
and ALSO implement things like ${1-default} that is more compact than the
current ifelse(`$1',,`default',`$1') in M4 parlance.
Sure, but doesn't that just delay the conversion
Ralf Wildenhues [EMAIL PROTECTED] writes:
http://lists.gnu.org/archive/html/libtool-patches/2005-01/msg00157.html
Thanks for mentiong that, I put the following into the Autoconf manual:
2007-01-28 Paul Eggert [EMAIL PROTECTED]
* doc/autoconf.texi (Shellology): pdksh 5.2.14 is still
12 matches
Mail list logo