From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <00d201c4e22b$ed889980$5e667d50@SOMA>
References: <b673d62582e4467c8823a7bd8718e391@terzarima.net>
	<Pine.LNX.4.58.0412141525330.23019@linux.site>
	<00d201c4e22b$ed889980$5e667d50@SOMA>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9E3DCD40-4E20-11D9-901F-00112430C042@gmail.com>
Content-Transfer-Encoding: 7bit
From: jim <jim.whitson@gmail.com>
Subject: Re: [9fans] (no subject)
Date: Tue, 14 Dec 2004 22:36:38 +0000
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Topicbox-Message-UUID: 1617c70c-eace-11e9-9e20-41e7f4b1d025


On 14 Dec 2004, at 22:26, boyd, rounin wrote:

> sounds right to me.  damn idiots.
>
If you'll pardon a humble mortal's ignorance, what's so bad about it? 
Well, re-phrase that -
how else to do accurate bit-packed structs like for tcp/ip headers? As 
I read this thread,
'packed' allows just that; it tells the compiler not to mess with how 
you've packed a given
struct. In which case, it seems pretty useful to me - I'd love to know 
how real coders do
tcp/ip headers :-S.

cheers,

jim