tgetent core dump on sco xenix

[Peter da Silva]

In article <3222 at bigtex.uucp>, james at bigtex.uucp (James Van Artsdalen) writes:
> IN article <701 at nod2sco>, rosso at sco.COM (Ross Oliver) wrote:
> > Here are a few tips to avoid problems like this in large-model
> > 286 programs:

> >     - Don't use "0" to mean NULL ( i.e. (char *)0 ).

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

He's speaking in the context of a function call. Large model 286
programs have 32 bit pointers but 16 bit integers, so if you pass
0 to a function expecting a pointer the stack will be off by two
bytes.

So, the problem isn't a broken compiler, it's a broken CPU architecture.
-- 
-- `-_-' Peter (have you hugged your wolf today) da Silva.
--   U   Ferranti International Controls Corporation.
-- Phone: 713-274-5180. CI$: 70216,1076. ICBM: 29 37 N / 95 36 W.
-- UUCP: {uunet,academ!uhnix1,bellcore!tness1}!sugar!ficc!peter.