Lacking <limits.h> (Was: Re: PAX won't make on my UNIX PC)

[Mark H. Colburn]

In article <2839 at osiris.UUCP> consult at osiris.UUCP (Unix Consultation Mailbox (Phil)) writes:
+In article <542 at jhereg.Jhereg.MN.ORG> mark at jhereg.MN.ORG (Mark H. Colburn) writes:
+>In article <17934 at vax5.CIT.CORNELL.EDU> jhc at vax5.cit.cornell.edu (James H. Cloos, Jr.) writes:
+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).

You're absolutely right.   I did misunderstand, and NeXT should supply a
version of limits.h. 

+
+>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?

It wasn't.  I simply pulled it out of ANSI and POSIX documentation.

-- 
Mark H. Colburn                  "Look into a child's eye;
Minnetech Consulting, Inc.        there's no hate and there's no lie;
mark at jhereg.mn.org                there's no black and there's no white."