Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site spanky.UUCP
Path: utzoo!linus!decvax!harpo!gummo!whuxlb!floyd!clyde!burl!spanky!ka
From: ka@spanky.UUCP (Kenneth Almquist)
Newsgroups: net.lang.c
Subject: Re: Funny bugs in some C compilers
Message-ID: <484@spanky.UUCP>
Date: Sat, 17-Sep-83 22:24:19 EDT
Article-I.D.: spanky.484
Posted: Sat Sep 17 22:24:19 1983
Date-Received: Tue, 20-Sep-83 17:40:48 EDT
References: <654@cwruecmp.UUCP> <815@watcgl.UUCP>
Organization: Bell Labs, Holmdel, N. J.
Lines: 12

Before we discuss how to implement structure comparison, we should
consider whether structure comparison should be implemented at
all.  I don't think it should.  I think that the number of programs
that could benefit from a structure comparison operator is quite
small.  (My opinion, anyone want to come up with a list of cases
where structure comparison would be useful?)  As a result, some
compiler implementers will probably not bother with structure
comparison and so that people will tend to avoid the feature to
ensure portability even if they do have a use for it.  In short,
I expect structure comparison to become known as a feature that
flopped if it is added to C.
						Kenneth Almquist