Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site galbp.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!galbp!bing
From: bing@galbp.UUCP (Bing Bang)
Newsgroups: net.lang.c
Subject: The one and only objection to C
Message-ID: <69@galbp.UUCP>
Date: Thu, 20-Dec-84 17:17:35 EST
Article-I.D.: galbp.69
Posted: Thu Dec 20 17:17:35 1984
Date-Received: Fri, 21-Dec-84 08:10:37 EST
Reply-To: bing@galbp.UUCP (Bing Bang)
Organization: Lanier Business Products, Inc., Atlanta, Georgia
Lines: 15

I love C. I think it's by far the best compiler based language that has ever
been produced.

I only have minor complaint:
why in the world does most C compilers insist on padding structures?

I am currently working on a network driver that needs to handle a data
packet that has a precise structure to it. It's easy to describe the
structure in C, but if the compiler puts in padding between fields, I can't
simply read in a packet on top of a structure. I must instead "jump" over
the padding bytes both going and comming.

"No, you stupid computer, do what I mean, not what I type!"
...akgua!galbp!bing