[net.micro.amiga] RAM: drive memory hog, K & R, and read-locks on files

dillon@PAVEPAWS.BERKELEY.EDU.UUCP (07/11/86)

	ok, ok... K & R doesn't say anything about specific lo-end sizes
for short and int..  BUT I would like to point out to those of you who
don't like the 'assume it's 32 bit' philosophy that by the standard
definition, you could also apply it to a 16 bit int... that is 'assume it's
at least 16 bits'... so I don't feel too bad about loosing the point.

	And now that the RAM: drive problem has been confirmed many times
over, I'm wondering if the people at Commodore would like to comment on it?
I'm dying to know why whoever-assumed-that got away with it (in terms of
not handling Write(fd, buf, some_small_value) correctly)....


Q: If two processes open the same file with MODE_OLDFILE, then both begin
writing to that file, will it work?  For example, say the file were 4K long,
the first program writes random junk in the first 2K, the second program 
writes random junk in the second 2K...  does amigados do the right thing,
or does it get confused??

				-Matt