User forums > Using Code::Blocks

Set to ANSI C standard?

<< < (2/5) > >>

drewvoros:
Thanks for the reply BlueHazzard,

I think I need to find out for sure from the prof. about the distinction of C90, C99, C11 standards. I'm hoping he knows because in his syllabus he definitely refers to C-Free as the "compiler" he will be using to grade :o

I will post back when I hear from him later this evening. Hopefully then I can clarify what I really need. Thanks for the help so far everyone!

drewvoros:
Oh by the way when I downloaded the recommended C-Free 4.0 the default compiler was mingw2.95
I'm assuming that is what the prof will be using because no instructions to change the compiler settings were given. Don't know if this helps any with more info.

Still waiting to hear back about the C90, C99, C11 distinction from the prof. Will update later tonight.

drewvoros:
So I heard back from my prof and I'm pretty sure he doesn't know anything about compilers because he responded with "I cannot verify anything about a product I never used" even after I listed all versions of the ANSI standards we've talked about.  >:(

So yes frustrating. But I know C-Free's  default compiler is MinGW 2.95. Any advice how to set the GNU GCC to behave similarly? Or any other suggestions?

stahta01:

--- Quote from: drewvoros on January 30, 2015, 03:52:03 am --- Or any other suggestions?

--- End quote ---

Install the exact compiler as being used by your stupid professor is the only true way.

But, 2.95 is so old it likely will NOT run on your computer.

Try C90 on your computer for development then test the code on another computer able to run 2.95.

Tim S.

thomas:

--- Quote from: drewvoros on January 29, 2015, 07:19:45 pm ---default compiler was mingw2.95  8) 8) 8)

Still waiting to hear back about the C90, C99, C11 distinction from the prof. Will update later tonight.
--- End quote ---
Um... yeah, right. MinGW-GCC 2.95. That's... a 14 year old MinGW build which uses a pretty shitty 16 year old version of GCC.  ;D

No need to worry about C99 or C11 then, they're out of the question with that compiler. It's reassuring when the teacher recommends one of the worst compilers in history...

Anyway, you will be using the --ansi -pedantic-errors command line options with that compiler. I don't know where you would put it in Free-C (which by the way seems to cost money, as opposed to "free"?), but presumably there are some kind of "project options" or global "compiler options" there just in the same way as in Code::Blocks.

I would recommend putting it directly in the compiler's options since that way you cannot accidentially forget doing so (which is bound to happen if you add it manually to each and every project).

Navigation

[0] Message Index

[#] Next page

[*] Previous page