Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!harpsichord.cis.ohio-state.edu!lwh
From: lwh@harpsichord.cis.ohio-state.edu (Loyde W Hales)
Newsgroups: comp.windows.x
Subject: Re: Retaining what is under a popup menu?
Keywords: popup menu save-under
Message-ID: <73465@tut.cis.ohio-state.edu>
Date: 31 Oct 89 17:24:06 GMT
References: <362@oscsuna.osc.edu> <363@oscsuna.osc.edu>
Sender: news@tut.cis.ohio-state.edu
Reply-To: Loyde W Hales <lwh@cis.ohio-state.edu>
Distribution: usa
Organization: Ohio State University Computer and Information Science
Lines: 37

In article <363@oscsuna.osc.edu> spencer@heinlein.osc.edu (Stephen N. Spencer) writes:

>But a question:  In Young's book, page 391, under the Shell class definition,
>why one of the Boolean default values is spelled "False" and the other two
>spelled "FALSE" ?  

Actually, the answer is rather stupid and quite C-related.  You see (or is
that ``you C''?), the X library of headers has declared the a ``boolean
type'' in two areas:

	Xlib.h		#define Bool int
			#define True 1
			#define False 0

	Intrinsic.h	typedef Boolean char
			#define FALSE 0
			#define TRUE  1

The former one, being defined at the Xlib level, is the accepted X-ology in
many ways.  The latter one is used by the Widget classes by definition; it is
also the C-normal way of doing things, where macro constants are ALL_CAPS.
(In fact, this definition of TRUE and FALSE are found in many C language
header files:  cgidefs.h, cmpinclude.h, curses.h, usercore.h, and often
stdargs.h.)

So, the bottom line is that both will work--in fact, they are technically
identical.

Yours,



-=-

                                Department of Computer and Information Science
Loyde W. Hales, II                      The Ohio State University
lwh@cis.ohio-state.edu          2036 Neil Avenue Mall, Columbus, Ohio  43201