On Mon, Dec 25, 2000 at 10:11:23AM -0500, Pavel Roskin wrote:
> > Yes, that version should have been named 3.x too, imho.
>
> No. We pretend to be fully compatible with correctly written
> configure.in's.
well, one reliable test for that is whether one can use the same
configure.in on old/new ve
Hello, Mirar!
> > Yes you may, but it will be 2.50. The fact that broken configure.in
> > no longer work is no surprise, and it could have happened in 2.15.
>
> Yes, that version should have been named 3.x too, imho.
No. We pretend to be fully compatible with correctly written
configure.in's.
Mirar wrote:
> And I *can* use every possible character inside a string; both the
> '\"' and '\042' mechanisms make sure of that. In a raw m4 environment,
> I don't have that possibility without changequote.
> Is that - define - going to be dropped too, btw?
You see :-). I do think AutoGen the
> "Mirar" == Mirar <[EMAIL PROTECTED]> writes:
Mirar> Yes, and M4's approach doesn't work well if you don't set up
Mirar> your macro library yourself. What I call black box is when
Mirar> someone else sets up and maintains something that you only get
Mirar> an API to, something you only can
> Mirar> Since m4 environment will not let you change the environment
> Mirar> (changequote) if you need to use quoting in macros, I think
> Mirar> this was a good idea. I think major the design miss was to use
> Mirar> m4 in the first place, since it doesn't work well in
> Mirar> API-to-black-box
> "Mirar" == Mirar <[EMAIL PROTECTED]> writes:
Mirar> Since m4 environment will not let you change the environment
Mirar> (changequote) if you need to use quoting in macros, I think
Mirar> this was a good idea. I think major the design miss was to use
Mirar> m4 in the first place, since it d
> Sorry, that's exactly the converse: what the heck is this idea that
> one can write program without paying attention to the programming
> language? M4 is a programming language, it comes with its rules, and
> if you disregard them, _you_ are wrong.
In this case, from my viewpoint, using quotin
> "Mirar" == Mirar <[EMAIL PROTECTED]> writes:
Mirar> After looking into things a little bit more today, I can say:
Mirar> What the heck is with this totally overexaggerated quoting in
Mirar> macros?
Sorry, that's exactly the converse: what the heck is this idea that
one can write program
> "Mirar" == Mirar <[EMAIL PROTECTED]> writes:
Mirar> Akim Demaille <[EMAIL PROTECTED]> writes:
>> > "Mirar" == Mirar <[EMAIL PROTECTED]> writes:
>>
>> >> # We need balanced brackets: [
Mirar> That solution works, but is darn ugly to have to use.
>> So use @>:@.
Mirar> Does that work i
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Mirar writes:
>
> > Does that work in older autoconfs? My problem is that it's a big team
> > of developers with different versions of autoconf (from the oldest
> > possible to the newest from CVS).
>
> Standardize on one (say, 2.13) and check the
> -Original Message-
> From: Akim Demaille [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 21, 2000 4:15 PM
> To: Bernard Dautrevaux
> Cc: 'Mirar'; Autoconf List
> Subject: Re: changequote
>
>
>
> AC_ARG_WITH(mmalloc,
> [ --wit
Mirar writes:
> Does that work in older autoconfs? My problem is that it's a big team
> of developers with different versions of autoconf (from the oldest
> possible to the newest from CVS).
Standardize on one (say, 2.13) and check the resulting configure script
into your revision control system
Akim Demaille <[EMAIL PROTECTED]> writes:
> > "Mirar" == Mirar <[EMAIL PROTECTED]> writes:
>
> >> # We need balanced brackets: [
> Mirar> That solution works, but is darn ugly to have to use.
>
> So use @>:@.
Does that work in older autoconfs? My problem is that it's a big team
of develop
AC_ARG_WITH(mmalloc,
[ --with-mmalloc Use memory mapped malloc package],
[case "${withval}" in
yes) want_mmalloc=true ;;
no) want_mmalloc=false;;
*)AC_MSG_ERROR(bad value ${withval} for GDB with-mmalloc option)
;;
esac],[want_mmalloc=false])dnl
> -Original Message-
> From: Mirar [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 20, 2000 6:21 PM
> To: Autoconf List
> Subject: changequote
>
>
> I have some problems with a newer autoconf,
> I have some code (I'm not the author) that looks like
>
> changequote({,})dnl
>
> "Mirar" == Mirar <[EMAIL PROTECTED]> writes:
>> # We need balanced brackets: [
Mirar> That solution works, but is darn ugly to have to use.
So use @>:@.
> # We need balanced brackets: [
That solution works, but is darn ugly to have to use.
/Mirar
On Thu, Dec 21, 2000 at 02:05:51PM +0100, Akim Demaille wrote:
: > "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
:
: Lars> Can't m4sugar's `m4_noquote' macro be used?
:
: Nope, inside the macro we really need the quote, but the argument he
: wants to give to AC_CACHE_VAL is not balanced =
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> Can't m4sugar's `m4_noquote' macro be used?
Nope, inside the macro we really need the quote, but the argument he
wants to give to AC_CACHE_VAL is not balanced => what would you give
to m4_noquote? An unbalanced argument, the very same
On Thu, Dec 21, 2000 at 12:54:19PM +0100, Akim Demaille wrote:
:
: > No, it means you cannot expect AC_MSG_CHECKING to keep on working
: > after having changed the quotes. Get rid of changequote. If you need
: > some help, post the snippet.
:
: Since I totally fail to work around, I would real
> No, it means you cannot expect AC_MSG_CHECKING to keep on working
> after having changed the quotes. Get rid of changequote. If you need
> some help, post the snippet.
Since I totally fail to work around, I would really appreciate some help.
This is how the original (before I started to wor
> No, it means you cannot expect AC_MSG_CHECKING to keep on working
> after having changed the quotes. Get rid of changequote. If you need
> some help, post the snippet.
Since I totally fail to work around, I would really appreciate some help.
This is how the original (before I started to work
| I have some problems with a newer autoconf,
| I have some code (I'm not the author) that looks like
|
| changequote({,})dnl
| 81: AC_MSG_CHECKING(for JAVA_HOME)
|
| and gives the following disaster:
|
| /usr/local/bin/autoheader: unexpected EOF while looking for `''
| /usr/local/bi
On Fri, Sep 08, 2000 at 09:05:57AM -0400, Pavel Roskin wrote:
: I'll try to remove changequote()s from libtool.m4 as long as it remains
: compatible with Autoconf-2.13
I don't see how this can be a problem - it's strictly an m4 parse issue,
and the m4 parsing is the same, no matter which autoconf
> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
Pavel> I'm fixed now :-)
:)
Pavel> I'll try to remove changequote()s from libtool.m4 as long as it
Pavel> remains compatible with Autoconf-2.13
This is totally independent from the Autoconf release.
Hello, Akim!
> Yes, this is a bad recommendation. And in fact you frightened me
> Pavel, by current you mean 2.13, right? I could not find this horror
> in the CVS documentation. But there is an answer to the above
> statement:
Sorry to all :-(
"info --file autoconf.info" looks in /usr/info b
| On Thu, Sep 07, 2000 at 02:12:34PM -0400, Pavel Roskin wrote:
| > -
| > 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 qu
On Thu, Sep 07, 2000 at 02:12:34PM -0400, Pavel Roskin wrote:
> -
> 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 charact
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' re
29 matches
Mail list logo
