You can login if you already have an account or register by clicking the button below.
Registering is free and all you need is a username and password. We never ask you for your e-mail.
Watching others use it whom are considered professionals. They use more than 1 compiler and GCC loves to spit out errors, more errors, and then bitch some more about something.
Code made runs after errors are ignored. The other compilers also run but don't bitch in the process of compiling.
[+]Master_Foo0 points0 points0 points
ago
(edited ago)
[–]Master_Foo0 points
0 points
0 points
(+0|-0)
ago
(edited ago)
If GCC is telling you that you have errors in your code, it's probably because your code isn't standards compliant. You probably forgot a semicolon somewhere.
Think about it. When a C / C++ standards are created, they are first implemented in GCC because that's what the developers use. So, if Visual Studio ISN'T warning you about something and GCC IS warning you about something, it's because Visual Studio ISN'T standards compliant.
Again, this isn't a problem with GCC. It's a problem with you being ignorant of the standard. I.E. GCC is working as expected. The problem is sitting somewhere between the chair and the keyboard.
view the rest of the comments →
[–] Master_Foo ago
It's not a matter of luck. It's a matter of being competent with my tools. You know, like a professional.
If you are having problems with GCC, you are probably a script kiddy. Quit blaming the tool and give yourself a stern evaluation.
[–] B3bomber ago
Watching others use it whom are considered professionals. They use more than 1 compiler and GCC loves to spit out errors, more errors, and then bitch some more about something.
Code made runs after errors are ignored. The other compilers also run but don't bitch in the process of compiling.
[–] Master_Foo ago (edited ago)
If GCC is telling you that you have errors in your code, it's probably because your code isn't standards compliant. You probably forgot a semicolon somewhere.
Think about it. When a C / C++ standards are created, they are first implemented in GCC because that's what the developers use. So, if Visual Studio ISN'T warning you about something and GCC IS warning you about something, it's because Visual Studio ISN'T standards compliant.
Again, this isn't a problem with GCC. It's a problem with you being ignorant of the standard. I.E. GCC is working as expected. The problem is sitting somewhere between the chair and the keyboard.