rokicki@rocky.STANFORD.EDU (Tomas Rokicki) (08/07/87)
C'mon, folks, let's check our facts before we post!
In each of Manx 3.20a, 3.40a, and 3.40b, the code
fragment
char *p ;
s() {
if (p==0) ;
if (!p) ;
}
compiles correctly, with a tst.l _p, bne pair for
each. There is no NULL bug in Manx, at least not
in 3.20a, 3.40a, or 3.40b; I've never had any
problems. So let's not spread this any further.
The main reason that NULL might be set to 0L
instead of 0 is so you can pass NULL as a pointer
argument to a function. That is why Manx has
NULL defined as 0L in each stdio.h file I have
received from them.
-tom
baumann@iaoobelix.UUCP (Joachim Baumann) (05/31/89)
Hi Amigaists, I have only a short question. I own Manx Aztec C 3.6A and want to know if this is the newest version and if it is not, if someone could post the patches(if there exists a version 3.6[BCDE]). Thanx in advance, J.Baumann Joachim Baumann Fraunhofer Institut fuer Arbeitswirtschaft und Organisation Holzgartenstrasse 17 D-7000 Stuttgart 1 West-Germany BITNET: iaoobel.uucp!baumann@unido.bitnet UUCP: ...{seismo!unido, pyramid}!baumann@iaoobel.UUCP Tel. +49/0711/121-3896 | 'It can hardly be a coincidence that no language on Earth has ever | produced the expression "as pretty as an airport".' | Douglas Adams, 'The long dark tea-time of the soul'