|
From: Andres R. <lo...@ho...> - 2002-04-20 17:40:39
|
Hello! =20 You are right. =96ansi does not generate any warnings. I useed it with =96pedantic option. I used MSYS and MinGW (latest, see below) >gcc -v gcc version 2.95.3-6 (mingw special) =20 I noticed that MinGW that ships with Dev-C++ 4.0(1) is slightly older. >gcc =96v gcc version 2.95.2 19991024 (release) =20 I tried it with Dev-C++ 4.1 and =84original=93 compiler. I got worning I mentioned. I tried it on command line and it =84worked=93 fine also. =20 Try playing around if you really want to see a little warning message ;) =20 Andres. =20 -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Bob Wilson Sent: Saturday, April 20, 2002 7:12 PM To: Dev-C++ User Mailing List Subject: Re: [Dev-C++] Dev-C++ Users Beware! =20 Andres, =20 If it is GNUC extension, that greatly relieves my concern, however none of the compiler switches you mention generate any warnings. I tried them individually and in combination in both the compiler options and the project options. It is possible that the Bloodshed IDE is not passing the switches properly to the compiler, but I doubt it.=20 =20 Regards, =20 Bob -Yes. Variable sized arrays are GNUC extension. =20 If you use =96ansi or =96pedantic switches on commandline, you get only warning: =20 test.cpp: In function `int main()': test.cpp:12: warning: ANSI C++ forbids variable-size array `myArray' =20 |