autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 0/5] more aggressive on ${a:-b}


From: Ralf Wildenhues
Subject: Re: [PATCH 0/5] more aggressive on ${a:-b}
Date: Thu, 26 Aug 2010 19:27:36 +0200
User-agent: Mutt/1.5.20 (2010-04-22)

Hi Eric,

* Eric Blake wrote on Thu, Aug 26, 2010 at 01:18:16AM CEST:
> On cygwin, attempts to do a glob() with a filename that contains
> a backslash can issue a warning; but I have been unable to reliably
> reproduce that in my environment (otherwise, I would have used it
> as an example in the second patch).  But see these links for an
> example of where unintended globbing matters:
> http://cygwin.com/ml/cygwin/2009-04/msg00531.html

I'm sure somebody thought that it would be a good idea to print that
warning, I can't imagine any reason that wouldn't outweigh its downsides
now though.  Do you have a link to the corresponding implementation
discussion?  Thanks.

> Eric Blake (5):
>   m4sh: fix some namespace safety issues

>   docs: mention cost of globbing during variable expansion

I'm replying to that one separately.

>   tests: improve some shell assumption testing
>   m4sh: reduce size of AS_VAR_TEST_SET

>   m4sh: assume ${a:-b} support

This one contains merge conflict markers, so cannot have been tested
in this spelling.  The tests in this one assume that unset works (I'm
not judging that, just stating that it's the case).

If you (still) need somebody to test IRIX, OSF, Solaris 2.6, AIX, please
ping me.  I definitely would feel a bit less worried if these changes
were thoroughly tested before the next release.

Thanks,
Ralf



reply via email to

[Prev in Thread] Current Thread [Next in Thread]