From owner-freebsd-current Mon Jun 17 13:53:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from dignus.com (sdsl-64-32-254-102.dsl.iad.megapath.net [64.32.254.102]) by hub.freebsd.org (Postfix) with ESMTP id 2578437B40C; Mon, 17 Jun 2002 13:52:57 -0700 (PDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.11.6/8.11.3) with ESMTP id g5HKkch83249; Mon, 17 Jun 2002 16:46:38 -0400 (EDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by lakes.dignus.com (8.11.6/8.11.3) id g5HKl4i52609; Mon, 17 Jun 2002 16:47:04 -0400 (EDT) (envelope-from rivers) Date: Mon, 17 Jun 2002 16:47:04 -0400 (EDT) From: Thomas David Rivers Message-Id: <200206172047.g5HKl4i52609@lakes.dignus.com> To: current@FreeBSD.ORG, mb@imp.ch, obrien@FreeBSD.ORG Subject: Re: PATCH: wchar_t is already defined in libstd++ In-Reply-To: <20020617124116.C22054@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "David O'Brien" wrote: > On Sun, Jun 16, 2002 at 10:57:32PM +0200, Martin Blapp wrote: > > On current, wchar_t is already defined in libstd++. This > > makes gcc baby cry. > > libstd++ should use our _BSD_WCAHR_T_ definitions, not its guesses at > what we use. Willing to make a patch to fix the libstdc++ headers? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Uh... In standard C++, wchar_t is a keyword. So, there should be no definition of wchar_t at all. I think this is the problem. (You can't typedef a predefined keyword.) (Now - the compiler should certainly have the very same idea of what a wchar_t is.. the same idea as the C typedef, but that's a gcc configuration problem.) - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message