🚀 go-pugleaf

In article <542@jhereg.Jhereg.MN.ORG> mark@jhereg.MN.ORG (Mark H. Colburn) writes:
>In article <17934@vax5.CIT.CORNELL.EDU> jhc@vax5.cit.cornell.edu (James H. Cloos, Jr.) writes:
>>It appears that the NeXTs are also lacking <limits.h>.  And that with gcc as
>>the standard compiler.
>
>I beleive it is not included because some of the values are somewhat
>hardware dependant.

Well, yeah, <limits.h> is (more than somewhat) hardware dependent... which
is certainly no reason *not* to include it in the distribution, but in fact
the exact opposite - it's not the kind of file you *can* port from another
random system without problems, so it *should* be distributed.  Maybe what
Mark Colburn said was based on misinterpreting James Cloos' statement to
mean that *gcc* was not distributed with limits.h (reasonable), when in
fact James meant that the NeXT was not shipped with <limits.h> as part of
its standard software (NOT reasonable).

>I have a limits.h which is the minimum required by
>ANSI and POSIX, you may use it if you like...

I looked at this and while it looks pretty close, I'll bet it doesn't work
on a NeXT (the 16-bit int and default unsigned char make me suspicious) -
what kind of system was this limits.h tweaked for?


phil