Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: what C needs
Message-ID: <7116@brl-smoke.ARPA>
Date: 18 Jan 88 01:03:38 GMT
References: <8712241909.AA03710@decwrl.dec.com> <6926@brl-smoke.ARPA> <496@doug.UUCP> <6995@brl-smoke.ARPA> <1128@jenny.cl.cam.ac.uk>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <1128@jenny.cl.cam.ac.uk> am@cl.cam.ac.uk (Alan Mycroft) writes:
-What about a machine which initialises its stack with parity errors
-...  How about
-    f2() { struct { char a; int b; } x;
-          x.a = 1, x.b = 1;
-          g2(x);
-       }

The implementation is not allowed to cause a trap when passing x to g2().
If it wants to flag holes specially so they cause a trap when touched,
then it will have to pass struct arguments member-by-member.