On Feb 14, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> - every macro becomes extremely picky on the quotes, since there is
> embedded code which really depends upon [ and ].
Can't this be done in a way that only traced macros become that picky?
This would allow for at least a soft transition.
> Well, Autoconf itself had no problem, but a certain package for
> portably building libraries has several times this code:
> changequote(<<, >>)dnl
> << --enable-shared[=PKGS] build shared libraries
>[default=>>AC_ENABLE_SHARED_DEFAULT],
> changequote([, ])dnl
Ugh! I swear it was not me who wrote that.
> So yes, the solution I propose it to transform m4's tracing output in
> order to re-feed m4 with that.
I really can't express with words how brilliant I consider this idea.
:-)
Go for it!
> Now if this idea is accepted, the question will be that of the format
> of the request. It can be directly the definition in m4,
> autoconf --trace AC_SUBST($1:$3)
> to ask just for the line number and the variable, separated with a
> colon.
Even though the internal tracing macros take the file name and the
line number as arguments $1 and $3, respectively, I don't think we
should expose this to the users. $1 should be the first actual
argument to the macro. We should probably do the translation
internally.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/ Enjoy Guaranį
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
