Path: utzoo!attcan!uunet!steinmetz!davidsen From: davidsen@steinmetz.ge.com (William E. Davidsen Jr) Newsgroups: comp.lang.c Subject: Re: const comparison in C and C++ Message-ID: <12184@steinmetz.ge.com> Date: 20 Sep 88 15:43:28 GMT References: <709@paris.ICS.UCI.EDU> <8500@smoke.ARPA> <1411@solo3.cs.vu.nl> <782@proxftl.UUCP> Reply-To: davidsen@crdos1.UUCP (bill davidsen) Organization: General Electric CRD, Schenectady, NY Lines: 19 In article <782@proxftl.UUCP> bill@proxftl.UUCP (T. William Wells) writes: | : | : const volatile int * const clock; /* clock is a readonly pointer to */ | : /* a readonly and volatile int */ | | Almost. As specified, it is not initialized and so contains a | null pointer. You should initialize it to the right address. Am I misreading the standard? My interpretation was that uninitialized global storage was set to *all bit zero* and that there was something that mentioned this might not be zero for types other than integral types. Is the compiler and linker path really supposed to initialize this to a null pointer (as in zero cast to a pointer)? On some machines the NULL pointer isn't all bits off, for sure. -- bill davidsen (wedu@ge-crd.arpa) {uunet | philabs}!steinmetz!crdos1!davidsen "Stupidity, like virtue, is its own reward" -me