From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8943 invoked from network); 31 May 2001 18:02:50 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 31 May 2001 18:02:50 -0000 Received: (qmail 6249 invoked by alias); 31 May 2001 18:02:42 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14626 Received: (qmail 6235 invoked from network); 31 May 2001 18:02:38 -0000 To: Clint Adams Cc: Bart Schaefer , Jos Backus , zsh-workers@sunsite.auc.dk, Au List Subject: Re: zsh and autoconf-2.50 References: <20010530144809.E47866@lizzy.bugworks.com> <010530150208.ZM3863@candle.brasslantern.com> <20010530184016.B3618@dman.com> <010530170846.ZM4077@candle.brasslantern.com> <20010531094055.A12930@dman.com> <20010531135143.A16261@dman.com> From: Akim Demaille Date: 31 May 2001 20:01:09 +0200 In-Reply-To: <20010531135143.A16261@dman.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (GTK) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: Akim Demaille | > So yes, define and undefine are undefined (in M4sh and M4sugar), but | > no, you should not know about this (in Autoconf), you should not be | > aware of it. | > | > What happens? | | % autoconf2.50 | configure.in:55: error: undefine: undefined: zsh-debug | configure.in:55: the top level | | The offending construct is here. | | undefine([zsh-debug])dnl | AC_ARG_ENABLE(zsh-debug, | [ --enable-zsh-debug compile with debug code and debugger symbols], | [if test x$enableval = xyes; then | AC_DEFINE(DEBUG) | fi]) This | configure.in:55: error: undefine: undefined: zsh-debug reads `there is an error declared by undefine: zsh-debug is undefined'. I agree the original `undefine' from M4 does not do that. I agree the message should be | configure.in:55: error: undefine: undefined macro: zsh-debug But by experience I know we need to be stricter to catch asap bad bugs, so I definitely prefer the 2.50 behavior. I'd use ifdef(,,undefine()).