On 8 Apr 2002, Akim Demaille wrote:
> Actually, YMMV. It depdends how `lucky' you were. Given that the
> name of the macro to be defined was not quoted, the macro was
> expanded. In typical cases, it gave more argument to define than 2,
> hence an error.
not really (I generally quote the argu
On Mon, Apr 08, 2002 at 08:44:44AM -0400, Thomas E. Dickey wrote:
> On 8 Apr 2002, Akim Demaille wrote:
>
> > Actually, YMMV. It depdends how `lucky' you were. Given that the
> > name of the macro to be defined was not quoted, the macro was
> > expanded. In typical cases, it gave more argument
On Mon, 8 Apr 2002 [EMAIL PROTECTED] wrote:
> On Mon, Apr 08, 2002 at 08:44:44AM -0400, Thomas E. Dickey wrote:
> > On 8 Apr 2002, Akim Demaille wrote:
> >
> > > Actually, YMMV. It depdends how `lucky' you were. Given that the
> > > name of the macro to be defined was not quoted, the macro was
> "Thomas" == Thomas E Dickey <[EMAIL PROTECTED]> writes:
Thomas> to reopen the wound since 2.5x adds salt).
>> 2.13 died on it. That's very different.
Thomas> no - 2.13 ignored it (I noticed this when I was making the
Thomas> macro for the prereq).
Actually, YMMV. It depdends how `lucky'
On 8 Apr 2002, Akim Demaille wrote:
> > "Thomas" == Thomas Dickey <[EMAIL PROTECTED]> writes:
>
> Thomas> sure there is - if they happen to have the same name as one of
> Thomas> autoconf's macros, the attempt at redefinition will be
> Thomas> ignored.
>
> Of course not.
>
> Thomas> (caveat -
> "Adam" == Adam J Richter <[EMAIL PROTECTED]> writes:
Adam> Dan Kegel <[EMAIL PROTECTED]> wrote:
>> Also, I'm pretty sure I've seen projects using macros that start
>> with AC_ (orbit has one, I think).
Adam> That should not be a problem. Autoconf only aborts this way
Adam> if it thinks
> "Thomas" == Thomas Dickey <[EMAIL PROTECTED]> writes:
Thomas> sure there is - if they happen to have the same name as one of
Thomas> autoconf's macros, the attempt at redefinition will be
Thomas> ignored.
Of course not.
Thomas> (caveat - I'm recalling this from 2.13 - haven't felt the nee
> "Dan" == Dan Kegel <[EMAIL PROTECTED]> writes:
Dan> Also, I'm pretty sure I've seen projects using macros that start
Dan> with AC_ (orbit has one, I think). Maybe they do this for macros
Dan> they want to propose for inclusion in autoconf. Will autoconf
Dan> choke on these, too?
No it w
> "Adam" == Adam J Richter <[EMAIL PROTECTED]> writes:
Adam> autoconf-2.53 does not allow AC_DEFINE_UNQUOTED variables that
Adam> begin with "AS_", reserving that part of the name space for
Adam> autoconf m4sugar macros. I think autoconf should allow this and
Adam> just issue a warning, bu
On Sun, Apr 07, 2002 at 05:17:40PM -0400, Peter Eisentraut wrote:
> Dan Kegel writes:
>
> > Also, I'm pretty sure I've seen projects using macros that start
> > with AC_ (orbit has one, I think). Maybe they do this for macros
> > they want to propose for inclusion in autoconf. Will autoconf
> >
Dan Kegel writes:
> Also, I'm pretty sure I've seen projects using macros that start
> with AC_ (orbit has one, I think). Maybe they do this for macros
> they want to propose for inclusion in autoconf. Will autoconf
> choke on these, too?
You're missing the point. The reason for this check is
On Sun, Apr 07, 2002 at 09:33:32AM -0700, Dan Kegel wrote:
> Also, I'm pretty sure I've seen projects using macros that start
> with AC_ (orbit has one, I think). Maybe they do this for macros
> they want to propose for inclusion in autoconf. Will autoconf
> choke on these, too?
to be consist
>there's no good reason for autoconf to start poaching on symbols that
>don't begin with AC_. File it as a bug in autoconf.
Recent versions of autoconf appear to split a lot of the autconf
functionality between autoconf proper and "m4 sugar." I think the
idea is that the m4sugar code co
Thomas Dickey wrote:
>
> On Sun, Apr 07, 2002 at 08:08:30AM -0700, Adam J. Richter wrote:
> > autoconf-2.53 does not allow AC_DEFINE_UNQUOTED variables
> > that begin with "AS_", reserving that part of the name space for
> > autoconf m4sugar macros. I think autoconf should allow this and
>
On Sun, Apr 07, 2002 at 09:16:19AM -0700, Adam J. Richter wrote:
> >there's no good reason for autoconf to start poaching on symbols that
> >don't begin with AC_. File it as a bug in autoconf.
>
> Recent versions of autoconf appear to split a lot of the autconf
> functionality between auto
Dan Kegel <[EMAIL PROTECTED]> wrote:
>Also, I'm pretty sure I've seen projects using macros that start
>with AC_ (orbit has one, I think).
That should not be a problem. Autoconf only aborts this way
if it thinks you are probably trying to use an autoconf macro and a
macro by that name is
On Sun, Apr 07, 2002 at 08:08:30AM -0700, Adam J. Richter wrote:
> autoconf-2.53 does not allow AC_DEFINE_UNQUOTED variables
> that begin with "AS_", reserving that part of the name space for
> autoconf m4sugar macros. I think autoconf should allow this and
> just issue a warning, but it wo
Sorry, I forgot to attach the actual patch to my previous
email.
Adam J. Richter __ __ 4880 Stevens Creek Blvd, Suite 104
[EMAIL PROTECTED] \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
18 matches
Mail list logo
