hello this is my first post
Im beginning to learn c programming
but i have some problems in my college they use old(ancient) compliers for c
I downloaded visual c++ express 2010
where it has alot of options win32, clr, general which option should select to open c editor
and if i open helloworld.c file which i created using notepad in MS visual C++ theres no debugging option
please can some show how they write c programs and compline in visual c++
thanks
Welcome to the forum!
There is a large video tutorial that you can d/l for working with visual express 2010. Your d/l website should have it.
It covers a LOT.
Create a new Console project. Add the helloworld.c file to the project. Compile and run.
First off, lets clear up one common misconception: "Newer" does not mean "better"Originally Posted by sharan01
hello this is my first post
Im beginning to learn c programming
but i have some problems in my college they use old(ancient) compliers for c
I downloaded visual c++ express 2010
If you want the best results from your course, you should use the same compilers they are using. You can't learn Biology from a text book on History.
If you want a relatively good --and free-- C-99 compiler that is still under active development try downloading a copy of Pelles C ...
smorgasbordet - Pelles C
I use it daily and it's very close to standards, with some really nifty extensions. It will compile for console, Windows and Windows CE in both 32 and 64 bit flavors... It also lets you make DLLs, LIBs, and RCs with internal support for visual resource editing.
As mentioned by rags_to_riches, you need to add the indicated source file to a project. Visual Studio does not allow you to open a random source file and just start debugging/compiling it unless it is a part of a project.
"Owners of dogs will have noticed that, if you provide them with food and water and shelter and affection, they will think you are god. Whereas owners of cats are compelled to realize that, if you provide them with food and water and shelter and affection, they draw the conclusion that they are gods."
-Christopher Hitchens
In main stream compilers, IMO it does.First off, lets clear up one common misconception: "Newer" does not mean "better"
I wouldn't say so. A C course shouldn't concentrate much on using the tools, only the basic usage in the beginning, and you can do that easily with Google. If the instructor uses some ancient tools, I would suggest using newer toolset.If you want the best results from your course, you should use the same compilers they are using.
For almost same reasons (minus "nifty extensions" and resources) I would suggest GCC, possibly in (near?) future clang.If you want a relatively good --and free-- C-99 compiler that is still under active development try downloading a copy of Pelles C ...
smorgasbordet - Pelles C
I use it daily and it's very close to standards, with some really nifty extensions. It will compile for console, Windows and Windows CE in both 32 and 64 bit flavors... It also lets you make DLLs, LIBs, and RCs with internal support for visual resource editing.
Well, it's been my experience that most software reaches a certain point where it's nearly as good as it's gonna get but then one more generation and it all goes to crap. I've seen many softwares (especially in the Shareware world where it's update or perish) go from modest beginnings to steallar half lives then on to garbage retirement. (I won't mention specific programs because I really don't need their authors mad at me)
From what I've seen GCC is pretty good. I haven't played with it enough to have a solid opinion about it... FWIW... Don't both Pelles and GCC come from LCC roots?For almost same reasons (minus "nifty extensions" and resources) I would suggest GCC, possibly in (near?) future clang.
But we all have our favorites...
