From owner-freebsd-questions Fri Dec 26 11:49:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29838 for questions-outgoing; Fri, 26 Dec 1997 11:49:32 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from BIGFUN.vwcom.com (BIGFUN.vwcom.com [151.197.101.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA29833 for ; Fri, 26 Dec 1997 11:49:29 -0800 (PST) (envelope-from bmc@WillsCreek.COM) Received: from WillsCreek.COM (gw.willscreek.com [151.197.101.46]) by BIGFUN.vwcom.com (8.8.6/8.8.6) with ESMTP id OAA05177; Fri, 26 Dec 1997 14:43:37 -0500 (EST) Received: from current.willscreek.com (current.willscreek.com [172.16.87.1]) by WillsCreek.COM (8.8.7/8.8.5) with ESMTP id OAA03555; Fri, 26 Dec 1997 14:48:18 -0500 (EST) Received: (from bmc@localhost) by current.willscreek.com (8.8.7/8.8.5) id OAA03115; Fri, 26 Dec 1997 14:48:17 -0500 (EST) Date: Fri, 26 Dec 1997 14:48:17 -0500 (EST) Message-Id: <199712261948.OAA03115@current.willscreek.com> From: Brian Clapper MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Greg Lehey Cc: Donn Miller , FreeBSD Questions Subject: Re: In-Reply-To: <19971225102031.22902@lemis.com> References: <19971225102031.22902@lemis.com> X-Mailer: VM 6.23 under Emacs 19.34.1 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 25 December, 1997, at 10:20 (+1030) Greg Lehey wrote: > On Wed, Dec 24, 1997 at 02:46:06PM -0800, Doug White wrote: > > On Tue, 23 Dec 1997, Donn Miller wrote: > > > >> Just wondering about the include file. FreeBSD doesn't seem to > >> have it. Does fbsd support this library? > > > > What's the name of the library or package? It may not come with the core > > system but may be available as a package. > > This question came up on -hackers in the last day or so in connection > with wine. The replies indicate that it's some kind of Microsoft > header file, and that it shouldn't be used under UNIX: there should be > some kind of #ifdef. You might like to check if that fits in with > what your package wants. Sorry, it's not (just) some kind of Microsoft header file; it's a new ANSI header file that provides support routines and definitions for wide characters. In addition to being provided by the MS Visual C++ development environment, it's available on Solaris 2.5. The functions/macros it provides are also available on other commercial Unices--such as Digital's version of OSF/1, HP/UX 10, and AIX 4.2--even though they don't provide the header file. (You include either or to get them, depending on the OS flavor.) I find I miss the functionality on FreeBSD, in fact, when I try to port certain software (namely stuff I'm doing at work) onto my boxes at home. P.J. Plauger's DinkumWare site (`http://www.dinkumware.com/') has this to say on the subject: `http://www.dinkumware.com/htm_cl/wctype.html#': Include the standard header to declare several functions that are useful for classifying and mapping codes from the target wide-character set. Every function that has a parameter of type wint_t can accept the value of the macro WEOF or any valid wide-character code (of type wchar_t). Thus, the argument can be the value returned by any of the functions: btowc, fgetwc, fputwc, getwc, getwchar, putwc, putwchar, towctrans, towlower, towupper, or ungetwc. You must not call these functions with other wide-character argument values. The wide-character classification functions are strongly related to the (byte) character classification functions. Each function isXXX has a corresponding wide-character classification function iswXXX. Thus, is analogous to : It provides macros such as islower(), iswupper(), towlower(), towupper(), iswpunct(), etc. Complete info is available at the above URL. (The topic index page is helpful; it's located here: `http://www.dinkumware.com/htm_cl/_index.html'.) According to `http://www.dinkumware.com/htm_cl/lib_over.html#Amendment', "The headers , , and are added with Amendment 1, an addition to the C Standard published in 1995." See `http://www.dinkumware.com/refc.html' for a "complete HTML description of the Standard C Library, corresponding to ISO/IEC 9899 (1990) as amended in 1995." ----- Brian Clapper, bmc@WillsCreek.COM, http://WWW.WillsCreek.COM/ Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them?