Mail Archives: djgpp/1997/03/12/23:45:01
From: | pv AT cs DOT montana DOT edu (Paul Peavyhouse)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | DJGPP inconsistencies?
|
Date: | Wed, 12 Mar 97 19:34:41 GMT
|
Organization: | Montana State University
|
Lines: | 41
|
Message-ID: | <5g7p5i$abl@netra.montana.edu>
|
NNTP-Posting-Host: | esus.cs.montana.edu
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
I have noticed a few inconsistencies with the DJGPP compiler over
other C compilers I use.
The first one is that the lines:
for(int i=0; i<256; i++)
{ someFunction(i);
}
won't compile SOMETIMES (?!?!?!), yet the lines:
int i;
for (i=0; i<256; i++)
{ someFunction(i);
}
works everytime...why?
Also, I sometimes get random compiler "parse" errors when I include
the following code in a program:
char *str;
if ( (str = getenv("DEM_PATH")) == NULL) {
printf("\"DEM_PATH\" environment variable not set\n");
exit(1);
}
Yet again...WHY?
I really like the DJGPP compiler (just wish I could make it work under
MSDEV) and the ease of porting to/fro UNIX/DOS. Makes college life a helluva
lot easier...but these compiler problems bother me as far as how "compatible"
DJGPP really is. Anyone have any comments?
PV
______________________________________________________________________________
Paul Peavyhouse
http://www.cs.montana.edu/~pv
email: pv AT cs DOT montana DOT edu
______________________________________________________________________________
- Raw text -