From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932174AbVHNT74 (ORCPT ); Sun, 14 Aug 2005 15:59:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932188AbVHNT74 (ORCPT ); Sun, 14 Aug 2005 15:59:56 -0400 Received: from mustang.oldcity.dca.net ([216.158.38.3]:4519 "HELO mustang.oldcity.dca.net") by vger.kernel.org with SMTP id S932174AbVHNT74 (ORCPT ); Sun, 14 Aug 2005 15:59:56 -0400 Subject: Re: [Patch] Support UTF-8 scripts From: Lee Revell To: Stephen Pollei Cc: Jason L Tibbitts III , "Martin v." =?ISO-8859-1?Q?L=F6wis?= , linux-kernel@vger.kernel.org In-Reply-To: References: <42FDE286.40707@v.loewis.de> <1123958572.11295.7.camel@mindpipe> Content-Type: text/plain; charset=windows-1251 Date: Sun, 14 Aug 2005 15:59:50 -0400 Message-Id: <1124049592.4918.2.camel@mindpipe> Mime-Version: 1.0 X-Mailer: Evolution 2.3.7 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2005-08-14 at 12:58 -0700, Stephen Pollei wrote: > My main point was that utf-8 for identifiers, operators, and string > constants are becoming more prevalent, so BOM support for scripts > sounds like a Good Idea™ . > I know the alternatives are available. That doesn't make it any less idiotic to use non ASCII characters as operators. I think it's a very slippery slope. We write code in ASCII, dammit. Lee