Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!seismo!brl-adm!brl-smoke!smoke!rbj@icst-cmr
From: rbj%icst-cmr@smoke.UUCP
Newsgroups: net.lang.c
Subject: Re: Address of array
Message-ID: <2375@brl-smoke.ARPA>
Date: Fri, 4-Apr-86 17:54:25 EST
Article-I.D.: brl-smok.2375
Posted: Fri Apr  4 17:54:25 1986
Date-Received: Wed, 9-Apr-86 07:54:34 EST
Sender: news@brl-smoke.ARPA
Lines: 26


	> Structure and array assignment, and comparison for equality, without buffer
	> copies is a good thing.
	
	You are aware, of course, that comparison for equality of structures,
	assuming it were added to the language, could not be implemented by a
	"string compare" instruction or code sequence?  Such a sequence would
	compare the padding bytes between structure members; there is no
	guarantee that those bytes are ever initialized, so two structures
	whose values are equal may not contain identical bit patterns.
	-- 
		Guy Harris
		{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
		guy@sun.arpa	(yes, really)
	
Fisrt, I disagree that struxure (or array) assignments are A Good Thing.
I much prefer the model of limiting primitive data types to values that
can be held in a register on an idealized machine. So much for the
`religious' part.

Secondly, struxures could be created with the padding bytes set to
all zero bits. Then, any garbage appearing in them could only be
creating by sloppy coding practices which even *I* abhor, even
considering my widely known nonportable tendencys.

	(Root Boy) Jim Cottrell		<rbj@cmr>