[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ada3a3a6xs6.fsf@roland-alpha.cisco.com>
Date: Wed, 16 Dec 2009 20:15:53 -0800
From: Roland Dreier <rdreier@...co.com>
To: Masami Hiramatsu <mhiramat@...hat.com>
Cc: Andrew Isaacson <adi@...are.com>, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org,
Rob Landley <rob@...dley.net>
Subject: Re: CONFIG_KPROBES=y build requires gawk
> For example, before the POSIX standard, to match alphanumeric charac-
> ters, you would have had to write /[A-Za-z0-9]/. If your character set
> had other alphabetic characters in it, this would not match them, and
> if your character set collated differently from ASCII, this might not
> even match the ASCII alphanumeric characters. With the POSIX character
> classes, you can write /[[:alnum:]]/, and this matches the alphabetic
> and numeric characters in your character set, no matter what it is.
I'm not sure I understand this, although I'm not a character set expert.
But is there really some possible locale + awk implementation where an
awk script, written in pure ASCII, operating on a pure ASCII input file,
will have [A-Za-z0-9] match a different set of ASCII characters than
[[:alnum:]] will match?
- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists