Path: utzoo!mnetor!uunet!husc6!yale!cmcl2!brl-adm!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: structure comparison
Message-ID: <10175@mimsy.UUCP>
Date: 14 Jan 88 04:40:33 GMT
References: <1322@sugar.UUCP> <1942@ho95e.ATT.COM> <1373@sugar.UUCP> <2456@ihlpe.ATT.COM>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 13

In article <2456@ihlpe.ATT.COM> woods@ihlpe.ATT.COM (Swan) writes:
>The problem is that the compiler cannot be sure how many bytes in the
>structures to compare for [in]equality.

This is easily solved by simply defining it to compare all elements
of the structure and no holes.  Unions become problematical, but
this, too, is easily solved, by outlawing comparison of things that
contain unions.

Yuck.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris