Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!udel!gatech!purdue!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: what C needs
Message-ID: <6995@brl-smoke.ARPA>
Date: 8 Jan 88 08:43:31 GMT
References: <8712241909.AA03710@decwrl.dec.com> <6926@brl-smoke.ARPA> <496@doug.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 7

In article <496@doug.UUCP> tim@doug.UUCP (Tim J Ihde) writes:
>Is the extra byte copied along, or is it filled with new-and-improved
>undefined garbage?

I don't think struct "holes" have guaranteed behavior one way or the other.
The destination hole might get random garbage, the source hole's contents,
0 fill, or be left unchanged, depending on the implementation.