Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!paperboy!husc6!encore!pinocchio.encore.com
From: jkenton@pinocchio.encore.com (Jeff Kenton)
Newsgroups: comp.arch
Subject: Re: RISC hard to program?
Message-ID: <12281@encore.Encore.COM>
Date: 23 Jul 90 17:38:41 GMT
References: <1878@charon.cwi.nl>
Sender: news@Encore.COM
Lines: 17

From article <1878@charon.cwi.nl>, by jack@cwi.nl (Jack Jansen):
> 
> I had to port some tcp/ip stuff to a strict alignment machine, and there
> is a 32-bit field on a non-32 bit boundary somewhere in the IP header
>

The "correct answer" to this seems to be something of a religious question.
It depends on whether you think network packets are defined as structures
or as byte streams.  If you call them structures you have both alignment
problems and big-endian/little-endian problems.  If you call them byte
streams you have neither problem, but the code looks uglier.


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      jeff kenton  ---	temporarily at jkenton@pinocchio.encore.com	 
		   ---  always at (617) 894-4508  ---
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -