Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!cam-news-hub1.bbnplanet.com!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Strict ANSI C headers for 2.1.5/lcc? Date: 2 Feb 1997 01:23:06 GMT Organization: Private BSD site, Dresden Lines: 19 Message-ID: <5d0q9q$694@uriah.heep.sax.de> References: <32F3B066.41C67EA6@acm.org> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34863 Gerd Moellmann <gerd@acm.org> wrote: > As the title says: Did someone the work to write ANSI headers > for FreeBSD and lcc (some system headers, e.g. runetype.h, contain > non-ANSI constructs like `long long'). That's hard to achieve, since those headers define the status quo of the system -- some of the syscalls and library functions actually do take 64-bit integer arguments. I'm not sure what happens if you compile with _ANSI_SOURCE, assuming that you don't need anything of the 64-bit interfaced functions. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)