[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AS_EXIT
From: |
Lars J. Aas |
Subject: |
Re: AS_EXIT |
Date: |
Wed, 1 Nov 2000 15:57:50 +0100 |
User-agent: |
Mutt/1.2.5i |
On Wed, Nov 01, 2000 at 09:47:07AM -0500, Pavel Roskin wrote:
: Hello, Lars!
:
: > AC_DEFUN([AS_NOP], [:]) # or `(exit $?)'?
:
: I guess you didn't study x86 architecture well. NOP doesn't change the
: flag register :-)
That's why I proposed (exit $?) instead, if status-preservation would be
an important consideration in the AS_NOP implementation :) However, there
are no places in autoconf where such a nop exist, to my knowledge (which
is quite superficial in great areas of autoconf though), and I doubt there
really is a need for it.
: > AC_DEFUN([AS_TRUE], [:])
: > AC_DEFUN([AS_FALSE], [(exit 1)]) # or `false'?
:
: I prefer to introduce new levels of macros (or functions or objects or
: whatever) when there is already some real stuff that needs to be split
: across the levels. At this stage I understand the problem better.
:
: I don't want to make any changes that don't fix any problem. This is not
: to say that I'll oppose if you make the patch.
Hmm, I just wanted to bring it up for discussion - but I see now that I
the thread is in autoconf-patches. I changed list to autoconf instead.
To any new readers, the question is whether creating macros named AS_NOP,
AS_TRUE, and AS_FALSE will make autoconf macros more readable....
Lars J
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: AS_EXIT,
Lars J. Aas <=