tgetent core dump on sco xenix

[James Van Artsdalen]

IN article <414 at vector.UUCP>, chip at vector.UUCP (Chip Rosenthal) wrote:
> In article <3222 at bigtex.uucp> james at bigtex.uucp wrote:
> }IN article <701 at nod2sco>, rosso at sco.COM (Ross Oliver) wrote:
> }>     - Declare your functions' return values.

> }This last statement is incorrect, or rather, evidence of a broken
> }compiler.

> XENIX does the right thing.  You can do (char *) assignments and
> comparisons with zero.

int *i, **p;

i = 0;
if (i != 0)
   printf("Broken compiler\n");

p = &i /* ie, not 0 */
if (p == 0)
   printf("Broken compiler\n");

Nobody is saying that "*i = 0; p = *i" needs to yield "p == 0".  But
the above tests should never fail or generate a warning under any
memory model.  I mean, if a compiler can handle

long l;

l = 0;

surely it can handle the "integer constant 0" business (and if it
doesn't handle either, you don't want it).  I can't remember if uPort
did this right with their 286 unix, but I expect better of SCO.
-- 
James R. Van Artsdalen   ...!ut-sally!utastro!bigtex!james   "Live Free or Die"
Home: 512-346-2444 Work: 328-0282; 110 Wild Basin Rd. Ste #230, Austin TX 78746