Date: Wed, 6 May 2009 17:20:00 +0400 From: Alexander Churanov <alexanderchuranov@gmail.com> To: Erik Trulsson <ertr1013@student.uu.se> Cc: freebsd-hackers@freebsd.org, Gabor Kovesdan <gabor@freebsd.org> Subject: Re: SoC 2009: BSD-licensed libiconv in base system Message-ID: <3cb459ed0905060620x78b98bcak5cea5570ee3120a9@mail.gmail.com> In-Reply-To: <20090506131312.GA48658@owl.midgard.homeip.net> References: <20090427183836.GA10793@zim.MIT.EDU> <20090427193326.GA7654@britannica.bec.de> <20090427194904.GA11137@zim.MIT.EDU> <49F6C7A1.6070708@FreeBSD.org> <20090428122225.GA2862@britannica.bec.de> <24e9a86bf5995ba551db8f27aa204191.squirrel@webmail.kovesdan.org> <20090428180624.GA2223@britannica.bec.de> <4A00B897.809@FreeBSD.org> <3cb459ed0905060328n4ad05d98xb5ba0c2e01d356e2@mail.gmail.com> <20090506131312.GA48658@owl.midgard.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/5/6 Erik Trulsson <ertr1013@student.uu.se>: > The C standard has very few requirements on wchar_t. =A0It is up to each > implementation to decide how wchar_t is defined. > There is nothing which prevents the FreeBSD project from deciding > that on FreeBSD wchar_t is always 32 bits wide, which can then be relied > upon in FreeBSD-specific code. =A0It is not like somebody else will chang= e > the relevant include files without warning. Ah, then wchar_t is for internal usage? Then it's OK. Alexander Churanov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3cb459ed0905060620x78b98bcak5cea5570ee3120a9>