Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!apple!bionet!agate!helios.ee.lbl.gov!nosc!ucsd!ucsdhub!esosun!seismo!uunet!mcvax!siebren
From: siebren@cwi.nl (Siebren van der Zee)
Newsgroups: comp.os.minix
Subject: Re: Minix/ST <stdio.h> problems.
Keywords: Yuck! No! NO PLEASE!
Message-ID: <7683@boring.cwi.nl>
Date: 27 Oct 88 12:47:19 GMT
References: <249@cstw01.UUCP>
Sender: news@cwi.nl
Organization: CWI, Amsterdam
Lines: 26

In article <249@cstw01.UUCP> meulenbr@cstw01.UUCP writes:
>Hi!
>
>I've encountered a number of problems using Minix/ST <stdio.h>.
>The major problem is that it defines NULL as 0.

The major problem is that you forgot that Minix is modelled after V7 unix.

>This is a killer on an ST since sizeof(char *) == 32 and sizeof(int) == 16.
>Solution: change the 0 in (char *)0

It has been a killer ever since 32-bit architectures showed up, but that's
not much of a problem: it kills braindamaged programmers. I consider this
a nice side-effect.

>Some other problems are encountered when a program tries to access the
>private part of a FILE struct (e.g. the count field, which is normally
>called cnt), or when someone refers to _iob (which is _io_table on
>Minix). I have a quick and dirty fix using defines, which fixes most of
			    ^^^^^
>these problems. The question is: should I post it (is there interest),

No! Please!!

	Siebren van der Zee, CWI Amsterdanm
	"A kernel a day keeps the users away."