* doc/autoconf.texi (Limitations of Builtins): Recommend using

AC_MSG_ERROR instead of exit.
        (Autoconf Language): Fix examples.
This commit is contained in:
Pavel Roskin 2000-10-27 17:29:23 +00:00
parent 6cb5583f10
commit 69a9124176
2 changed files with 10 additions and 4 deletions

View File

@ -1,3 +1,9 @@
2000-10-27 Pavel Roskin <proski@gnu.org>
* doc/autoconf.texi (Limitations of Builtins): Recommend using
AC_MSG_ERROR instead of exit.
(Autoconf Language): Fix examples.
2000-10-27 Pavel Roskin <proski@gnu.org>
* tests/suite.at: Move "-*- Autoconf -*-" to the second line.

View File

@ -739,7 +739,7 @@ has continuously been misunderstood... The rule of thumb is that
i.e., expect one level of quotes to be lost. For instance
@example
AC_COMPILE_IFELSE([char b[10];],, (exit 1); exit)
AC_COMPILE_IFELSE([char b[10];],, [AC_MSG_ERROR([you lose])])
@end example
@noindent
@ -752,7 +752,7 @@ argument to be understood as a literal, and therefore it must be quoted
twice:
@example
AC_COMPILE_IFELSE([[char b[10];]],, (exit 1); exit)
AC_COMPILE_IFELSE([[char b[10];]],, [AC_MSG_ERROR([you lose])])
@end example
@noindent
@ -5313,8 +5313,8 @@ invoker can tell that an error occurred.
Unfortunately, in some shells, such as Solaris 8 @command{sh}, an exit
trap ignores the @code{exit} command's status. In these shells, a trap
cannot determine whether it was invoked by plain @code{exit} or by
@code{exit 1}. To work around this problem, use @code{(exit 1); exit}
instead of @samp{exit 1}.
@code{exit 1}. Instead of calling @code{exit} directly, use the
@code{AC_MSG_ERROR} macro that has a workaround for this problem.
@item @command{export}
@cindex @command{export}