Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!munnari.oz.au!mimir!hugin!augean!chook.ua.oz!cagney
From: cagney@chook.ua.oz (Andrew Cagney - aka Noid)
Newsgroups: comp.os.minix
Subject: What's the future of VOIDSTAR et.al. in 1.4b?
Keywords: ansi __STDC_ VOIDSTAR VOID SYZET :-)
Message-ID: <647@augean.OZ>
Date: 10 Nov 89 04:11:17 GMT
Sender: news@augean.OZ
Reply-To: cagney@chook.ua.oz (Andrew Cagney - aka Noid)
Organization: Comp Sci, Uni of Adelaide, Australia
Lines: 24

I'm compiling some minix tools using an ansi compiler and hitting
compability problems. Specifically in dd.c there is the declaration
and call:

	int over();
	...
	signal(SIGINT, over);

Which in ansi-c, I understand to be invalid as the second parameter to signal
should be declared as:

	void *over();

Minix 1.4a, in several places, uses the symbol VOIDSTAR in an attempt
to get arround this incompability. So it would be declared as

	VOIDSTAR over();

And when compiling under ansi-c you would define VOIDSTAR=void* etc

Is this going to become the accepted way of doing these declarations or
will some other method be adopted?

					Andrew Cagney