Hello, Lars!
I'm moving the discussion to [EMAIL PROTECTED] where it seems more
appropriate.
>From the discussion in [EMAIL PROTECTED]
> : # Check for any special shared library compilation flags.
> : -changequote(,)dnl
> : if test -n "$ac_cv_prog_cc_shlib"; then
> : AC_MSG_WARN([\`$CC' requires \`$ac_cv_prog_cc_shlib' to build shared libraries])
> : + changequote(,)dnl
> : if echo "$old_CC $old_CFLAGS " | egrep -e "[ ]$ac_cv_prog_cc_shlib[ ]"
>>/dev/null; then :
> : + changequote([,])dnl
>
> Why not remove the changequote macros completely and use:
> if echo "$old_CC $old_CFLAGS " | egrep -e "[[ ]]$ac_cv_prog_cc_shlib[[
> ]]" >/dev/null; then :
The current autoconf documentation recommends using changequote:
-------------
However, in a few places the macros need to use brackets (usually in C
program text or regular expressions). In those places, they use the `m4'
builtin command `changequote' to temporarily change the quote characters
to `<<' and `>>'.
-------------
Shouldn't using double square brackets be considered a better solution?
This would avoid exposing m4 internals to configure.in writers. Also using
autoconf macros while non-standard quotes are in effect causes big
problems (as the recent example of libtool shows).
Shouldn't the documentation be changed?
Regards,
Pavel Roskin
