Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!nic.MR.NET!shamash!com50!jhereg!mark From: mark@jhereg.Jhereg.MN.ORG (Mark H. Colburn) Newsgroups: comp.sources.bugs Subject: Re: Lacking (Was: Re: PAX won't make on my UNIX PC) Message-ID: <555@jhereg.Jhereg.MN.ORG> Date: 15 Feb 89 05:42:34 GMT References: <550@kosman.UUCP> <523@jhereg.Jhereg.MN.ORG> <17934@vax5.CIT.CORNELL.EDU> <542@jhereg.Jhereg.MN.ORG> <2839@osiris.UUCP> Reply-To: mark@jhereg.MN.ORG (Mark H. Colburn) Organization: Minnetech Consulting, Inc., St. Paul MN Lines: 26 In article <2839@osiris.UUCP> consult@osiris.UUCP (Unix Consultation Mailbox (Phil)) writes: +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: +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 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@jhereg.mn.org there's no black and there's no white."