Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!cbmvax!vu-vlsi!perry
From: perry@vu-vlsi.UUCP
Newsgroups: comp.lang.c
Subject: Re: C struct definition according to K & R.
Message-ID: <649@vu-vlsi.UUCP>
Date: Wed, 11-Mar-87 01:48:13 EST
Article-I.D.: vu-vlsi.649
Posted: Wed Mar 11 01:48:13 1987
Date-Received: Thu, 12-Mar-87 21:14:58 EST
References: <9929@sri-spam.istc.sri.com>
Reply-To: perry@vu-vlsi.UUCP (Rick Perry)
Organization: Villanova Univ. EE Dept.
Lines: 28
Keywords: May structs have similar member names in dissimilar order?

In article <9929@sri-spam.istc.sri.com>
 robert@sri-spam.istc.sri.com (Robert Allen) writes:
> ..
>    In short, I believe that K&R were saying, "while constructs
>    such as this (above) may cause problems in some languages, they don't in
>    C."

   I agree with that, and so does our compiler (Pyramid 90x OSx3.1) after
adding some semicolons after the struct's { }

	    struct s1 {
		int i;
		long l;
	    };

	    struct s2 {
		long i;
		int l;
	    };

>     on the net, please include the # of years you've been using C, and which
>     machines/compilers you use.  Thanks!

  I've been using C for 0.000000E+00 years, no machines or compilers, I
just compile and execute it by inspection.

...Rick			..{cbmvax,pyrnj,bpa}!vu-vlsi!perry
			perry@vuvaxcom.bitnet