From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24078 invoked by alias); 21 Mar 2011 18:46:13 -0000 Received: (qmail 23989 invoked by uid 22791); 21 Mar 2011 18:46:12 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 21 Mar 2011 18:46:05 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LIF00C007YT2600@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Mon, 21 Mar 2011 20:44:39 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.126.16.52]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LIF00AP482EWOC0@a-mtaout20.012.net.il>; Mon, 21 Mar 2011 20:44:39 +0200 (IST) Date: Mon, 21 Mar 2011 20:10:00 -0000 From: Eli Zaretskii Subject: Re: [RFC] Question about CODESET macro inside config/djgpp/langinfo.h In-reply-to: <201103211612.p2LGCbYU010335@glazunov.sibelius.xs4all.nl> To: Mark Kettenis Cc: pierre.muller@ics-cnrs.unistra.fr, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <8362rc9uu9.fsf@gnu.org> References: <000c01cbe7e0$53e3f510$fbabdf30$%muller@ics-cnrs.unistra.fr> <201103211612.p2LGCbYU010335@glazunov.sibelius.xs4all.nl> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-03/txt/msg00969.txt.bz2 > Date: Mon, 21 Mar 2011 17:12:37 +0100 (CET) > From: Mark Kettenis > CC: gdb-patches@sourceware.org, eliz@gnu.org > > > From: "Pierre Muller" > > Cc: "'Eli Zaretskii'" > > > > Also about macros removal inside config subdirectory: > > > > I was wondering about the usefulness of CODESET macro definition > > inside > > config/djgpp/langinfo.h > > > > #define CODESET CODESET > > > > while CODESET is itself a member of an enumeration. > > It means that you can check for the macro using #ifdef. I think that > is required by POSIX. I'm not sure it's required, but every implementation I've seen has this macro, so I put it in as well.