delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:6976 |
From: | krecik AT ii DOT uni DOT wroc DOT pl (Grzegorz Nowakowski) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: DJGPP HELP!!!!! |
Date: | 08 Aug 1996 08:53:41 GMT |
Organization: | Laboratoire de Recherche en Informatique, UPS/CNRS, Orsay,FRANCE |
Lines: | 22 |
Message-ID: | <KRECIK.96Aug8105341@ii.uni.wroc.pl> |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 960808085610 DOT 19168D-100000 AT is> |
NNTP-Posting-Host: | hp20.lri.fr |
In-reply-to: | Eli Zaretskii's message of Thu, 8 Aug 1996 07:01:32 GMT |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
In article <Pine DOT SUN DOT 3 DOT 91 DOT 960808085610 DOT 19168D-100000 AT is> Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> writes: > That probably means that the program you are trying to port uses some > non-ANSI features (like header files and library functions which ANSI > doesn't mention). Strict ANSI C code will compile on any ANSI-compliant > compiler without any problems (and in my experience, it does). > Unfortunately, too few people restrict themselves to ANSI C when they > write programs... Is there ANSI C specification available on-line? Actually, when I want to write clean code, the only reference I have is BC 3.1 help (which points if such function is in ANSI C or not). And that's the main reason I keep the compilet on my HD. :-( -- Grzegorz Nowakowski <krecik AT ii DOT uni DOT wroc DOT pl> -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GC dpu s:- a- C++(++++) ULSH P+>+++ L+>++++ E+(+++) W N++ o? K? w---() O? M- V? PS PE Y+ PGP-@ t+ 5? X? R+@ tv--- b+(+++) DI? D+ G e-> h* r-- y ------END GEEK CODE BLOCK------ finger hayden AT vax1 DOT mankato DOT msus DOT edu for info about geek codes
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |