From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26031 invoked by alias); 5 May 2004 12:33:04 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 26020 invoked from network); 5 May 2004 12:33:03 -0000 Received: from unknown (HELO netezza.com) (209.113.240.37) by sources.redhat.com with SMTP; 5 May 2004 12:33:03 -0000 Received: from mail2.netezza.com (exchange [192.168.0.240]) by netezza.com (8.12.10+Sun/8.12.10) with ESMTP id i45CX234009694 for ; Wed, 5 May 2004 08:33:02 -0400 (EDT) From: John Yates Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: anything more stringent than -Wchar-subscripts ? Date: Wed, 05 May 2004 12:33:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: To: X-SW-Source: 2004-05/txt/msg00059.txt.bz2 I would like to ban use of unqualified char in all of our code. Beyond purging such usage from our current code base I need a way to identify any time that such usage reappears. I don't see anything in the current documentation that will let me do this. Have I missed something? /john -- John S. Yates, Jr. 508 665-6897 (voice) Netezza Inc 508 665-6811 (fax) 200 Crossing Blvd. Framingham, MA 01701 =20