Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!emory!hubcap!gatech!udel!mmdf
From: HBO043%DJUKFA11.BITNET@cunyvm.cuny.edu (Christoph van Wuellen)
Newsgroups: comp.os.minix
Subject: Re: use only short and long (not int) in struct message
Message-ID: <41247@nigel.ee.udel.edu>
Date: 9 Jan 91 16:18:09 GMT
Sender: mmdf@ee.udel.edu
Lines: 14

Well, int16 int32 etc are appropriate if the different parts which
communicate are compiled not only in 16 or 32-bit mode, but also by
incompatible compilers.

In this case, different alignment/padding etc of structures may do
any damage, but of course, it is more general to write int16, int32.

The real point is that FS must be modified to accept 'long' nbyte parameters
for read(fd, buf, nbyte) and write(fd, buf, nbyte)

It should be no problem if fd is cast to short, but nbyte should ALWAYS be
long to support user programs with int==long.

C.v.W.