actually be good if
the default behaviour of glibc was to report a regex compilation error
in that case, or maybe even better, print a warning like "\d: unknown
special character, treating as literal".
Of course, POSIX doesn't specify either \s or \d, just the
[:space:] and [:digi
On Thu, Nov 28, 2013 at 12:40:34PM -0500, Chet Ramey wrote:
> On 11/28/13, 7:23 AM, Peter Cordes wrote:
> > I submitted this on savannah a couple days ago:
> > https://savannah.gnu.org/support/?108450
> >
> > As I said there, the warning message for bash re-using a
something weird that wasn't my fault.
Oh, also, the online bug-bash archive has a bad habbit of replacing
code with address@hidden. There was a whole thread about setting
PS1=whatever that is now a complete mystery to non-subscribers!
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter
e only odd thing I found while playing around
with this is that printf %c only prints the first byte of the UTF-8
representation of a multi-byte character. (POSIX says to be
"extremely cautious" about using %c with wide characters, apparently
for good reason.)
--
#define X(x,y) x##y
Pete
