Hello all,
Why does void main(void) generate a warning message on some compilers (for example the GNU compiler) whereas it works fine for compilers from some other vendors (e.g. Borland’s Turbo C/C++ Compiler). Is there any compiler option available in the compiler to turn this message off?
You should't turn it off, instead use int main
http://faq.cprogramming.com/cgi-bin/...&id=1043284376
You should prefer the compiler that gives you more warnings over the compiler that silently compiles the wrong code
All problems in computer science can be solved by another level of indirection,
except for the problem of too many layers of indirection.
– David J. Wheeler
> Is there any compiler option available in the compiler to turn this message off?
Yes, do it properly and say
int main
Problem solved.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
No one gave me a good explanation I asked about why not about what should I do?
because C has a standard that defines that main returns int and not void.
If a compiler happens to accept void as return type its coincidence, so this code will compile on some compilers and not on others. Therefore some compilers choose to accept void but give a warning that this is crappy and you should turn this into int so it will compiler on *all* compilers
Good,
But how I can turn this warning message off from compilers such as Dev-C++
by typing int main(void)Originally Posted by alalam5
> No one gave me a good explanation I asked about why not about what should I do?
So you didn't click on the FAQ link posted by Vart then?
> But how I can turn this warning message off from compilers such as Dev-C++
By learning how to do it properly and declaring int main
EVERY single compiler will do something crappy with respect to the standard at some point (like not warning you about void main). The only defence in your programming is to make sure your code is ANSI-C and not whatever your current compiler will let you get away with.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
whats so hard about typing "int main()"? You sound like once of those half c++ converts who has to litter everything up and fight tooth and nail for your c++ ways. Follow the standard that way when you write in linux and want it to work in your dual booted windows (with Grub or bootcamp). To answer your question about the GNU complier why dont you post that in the "Linux Programming" section, but again it would be illogical to turn of a warning that keep you up with standard. If you where wondering the reason why you dont have to place void main() is because some where or some how in ANSI its set to auto place the void if need so just chill homeboy
You rant and rave about it, but at the end of the day, it doesn't matter if people use it as long as you don't see.
People are free to read the arguments, but if the only way for you to discover gravity is by jumping off a cliff, then that is what you're going to have to experience for yourself.
Eventually, this "fast and loose" approach of yours will bite you one too many times, then you'll figure out the correct way to do things. - Salem
All you need to know is right here
