Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935737AbZLQEQ0 (ORCPT ); Wed, 16 Dec 2009 23:16:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S936389AbZLQEQF (ORCPT ); Wed, 16 Dec 2009 23:16:05 -0500 Received: from sj-iport-6.cisco.com ([171.71.176.117]:64402 "EHLO sj-iport-6.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936385AbZLQEPz (ORCPT ); Wed, 16 Dec 2009 23:15:55 -0500 Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAE8/KUurR7H+/2dsb2JhbAC+WZZ/hCsE X-IronPort-AV: E=Sophos;i="4.47,410,1257120000"; d="scan'208";a="451079731" From: Roland Dreier To: Masami Hiramatsu Cc: Andrew Isaacson , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, Rob Landley Subject: Re: CONFIG_KPROBES=y build requires gawk References: <20091216235617.GA12267@hexapodia.org> <4B29A686.9070603@redhat.com> X-Message-Flag: Warning: May contain useful information Date: Wed, 16 Dec 2009 20:15:53 -0800 In-Reply-To: <4B29A686.9070603@redhat.com> (Masami Hiramatsu's message of "Wed, 16 Dec 2009 22:33:26 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-OriginalArrivalTime: 17 Dec 2009 04:15:53.0563 (UTC) FILETIME=[9FAB8AB0:01CA7ECF] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1134 Lines: 21 > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/