Path: utzoo!attcan!uunet!auspex!guy From: guy@auspex.auspex.com (Guy Harris) Newsgroups: comp.soft-sys.andrew Subject: Re: WP bug on SPARC, new release version? Message-ID: <2657@auspex.auspex.com> Date: 21 Nov 89 22:36:23 GMT References: Reply-To: guy@auspex.auspex.com (Guy Harris) Organization: Auspex Systems, Santa Clara Lines: 18 >i've discovered a bug in the wp code on SPARC. actually, it's a bug in >Sun's SPARC C compiler that's exercised by wp. (Actually, it's a bug in the WP code, which happens not to prevent it from doing what you want on many C implementations, but the SPARC and perhaps Pyramid C implementations are not among them; passing an object of type "foo" to a routine expecting an object of a union type that includes type "foo" is not valid C.) Is it ever the case that somebody passes something to "wp_DeAllocate" and doesn't know which of the N flavors of things that "wp_DeAllocate" can deallocate it is? If not, perhaps the best long-term fix is to replace "wp_DeAllocate" with multiple deallocaters and call the correct one in each instance, passing it a pointer to a "wp_PrimeKeySet" or to a "struct wp_SrchToken". (I.e., does all the code that calls it passing it a "struct wp_SrchToken *" really truly pass it a pointer to a "wp_SrchToken", not a pointer to a "wp_PrimeKeySet" in disguise, and *vice versa*?)