[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Don't expose AC_{COMPILE, LINK}_IFELSE internals in document
From: |
Ralf Wildenhues |
Subject: |
Re: [PATCH] Don't expose AC_{COMPILE, LINK}_IFELSE internals in documentation. |
Date: |
Tue, 1 Jun 2010 19:20:29 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
Hello Stefano,
* Stefano Lattarini wrote on Tue, May 25, 2010 at 07:15:38PM CEST:
> > > better to document external variables like $EXEEXT than to expose
> > > internal details like $ac_exeext; so it seems like AC_LINK_IFELSE
> > > should be the subject of the patch.
> >
> > And AC_COMPILE_IFELSE too, since its documentation mentions
> > $ac_object.
> Subject: [PATCH] Don't expose AC_{COMPILE,LINK}_IFELSE internals in
> documentation.
>
> * doc/autoconf.texi (Runtime) <AC_LINK_IFELSE>: Suggest to use
> `conftest$EXEEXT' rather than `conftest$ac_exeext' to acces the
> just-linked program file.
> (Runtime) <AC_COMPILE_IFELSE>: Suggest to use `conftest.$OBJEXT'
> rather than `conftest.$ac_object' to access the just-compiled
> object file. Also, refer to the object file as "just-compiled"
> rather than "just-linked".
I don't mind this patch, and it has been applied since, but I'll note
that we cannot reasonably expect $ac_objext and $ac_exeext to be
internal details, subject to change. The contents of $ac_compile and
$ac_link are, unfortunately, exposed and practically part of the API.
Cheers,
Ralf
- Re: [PATCH] Don't expose AC_{COMPILE, LINK}_IFELSE internals in documentation.,
Ralf Wildenhues <=