What is your most used compiler when you work with C/C++:
MS Visual Studio
Borland
GCC
Other paid (Please post)
Other free (Please post)
Other open-source (Please post)
What is your most used compiler when you work with C/C++:
Last edited by Devil Panther; 07-15-2009 at 08:47 AM.
"I don't suffer from insanity but enjoy every minute of it" - Edgar Allen Poe
http://www.Bloodware.net - Developing free software for the community.
I generally use gcc. From the command line (hate IDE's).
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
I prefer IDE's over command line, that's why I use MSVS. They are easy to handle in my opinion. But I'm sure I even dont know about 1% of all its function. Before MSVS, I was using borland.
HOPE YOU UNDERSTAND.......
By associating with wise people you will become wise yourself
It's fine to celebrate success but it is more important to heed the lessons of failure
We've got to put a lot of money into changing behavior
PC specifications- 512MB RAM, Windows XP sp3, 2.79 GHz pentium D.
IDE- Microsoft Visual Studio 2008 Express Edition
>> Before MSVS, I was using borland.
I used Borland compilers for many years, and can honestly say they are my favorite to work with. Probably the "fastest" compiler ever built, too.
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
Moved to General Discussions - a better home for polls.
Oh, and MSVC++ 2005 or the most recent version of GCC depending on what I'm doing and on what platform
Ditto. Except I will say "always" instead of "generally". After observing things around cboard, I have to say I have zero temptation to change this. Plus I'm a linux guy, of course, so maybe I don't have that much choice in the matter anyway. Which makes me doubly glad that gcc is gcc.Originally Posted by Sebastiani
I won't go off on IDE's beyond saying that while they may be great for professionals I think they are a very bad idea for beginners (again based on observations at cboard) who would be better off using the command line and a decent text editor. Which makes it a shame that some (non gcc) compilers don't give you that choice.
Last edited by MK27; 07-15-2009 at 09:35 AM.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
I sincerely disagree, but of course, this is subjective.
I would think beginners are more confused with command lines than with IDEs that does it all for them.
Anyway, I'm an all-around Visual Studio user. I have occasionally used GCC with Code::Blocks, but that's about it.
Btw, Visual Studio is not a compiler; it is an IDE. Visual C++ (and Visual C?) is the compiler(s).
>> Visual C++ (and Visual C?) is the compiler(s).
The actual compiler as invoked from the command line is cl (last time I used it anyway).
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
Yes, but while being confused by an IDE is no real cause for tears, wanting to be a computer programmer who doesn't use the command line sounds almost oxymoronic. They should be comfortable with CLI *before* they start programming IMO. And I bet if they were, they would not seem to have so much trouble with the IDE.
Ie, if you are a programmer, IMO the IDE is optional, but the command line is not. Sorry.
I don't think the "beginners" to which I referred are command line wizards who have been baffled by a set of drop down menus and a mouse, if you see my subjective opinionMore like they are victims of a specific, particular situation on a specific, particular operating system.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
Yes, the executable name is cl.exe. But the compiler's actual name is Visual C++ or Visual C.
I don't know. That seems very subjective since you are a Linux user.
I see no problem not knowing CLI if you're just developing normal Windows apps. Most of them do not deal with a lot of CLI stuff.
That also seems very subjective to me.Ie, if you are a programmer, IMO the IDE is optional, but the command line is not. Sorry.
I'd say the other way around.
Specific problems? But then would it matter if they are CLI gurus or IDE gurus, or am I way off what you meant here?More like they are victims of a specific, particular situation on a specific, particular operating system.
>> Yes, the executable name is cl.exe. But the compiler's actual name is Visual C++ or Visual C.
No, the name of the *package* is Visual C++. The name of the compiler is cl. Just ask the command prompt.
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
Yes, specific problems. You said it yourself:
If that is *all* you are going to do, fair enough. But this disguises the fact that Windows is a specialized environment relative to any other sort of programming, eg embedded, for the web, or if you were to work on a cross platform compiler or language or a database engine or anything that is not just a windows desktop app. All of those things are now going to be problematic for you if you have grown up ignoring the command line and therefore the fundamental basics of what an operating system *really* is (not what a particular OS ended up like on the surface).That seems very subjective since you are a Linux user.
I see no problem not knowing CLI if you're just developing normal Windows apps. Most of them do not deal with a lot of CLI stuff.
The "subjectiveness" of linux use is not a parallel to this at all, since while it may not be as widespread on home PC's, it is much more closely related to unix (almost a unix clone) meaning it has a much greater "heritage" in computer science generally. I'm not bashing MS or claiming that ultimately linux is better, just that the MS OS is more of an exception, whereas *nix should be considered "the rule". Witness, this is not about linux users who can't use windows -- they can -- it is about windows users who can't use linux, presuming it is a minor sort of fad, as opposed to a limb of the real elephant, UNIX.
One day in the future, programming may really become moving little icons around with your mouse. But we ain't there yet...
Package as in the pretty cardboard box?No, the name of the *package* is Visual C++. The name of the compiler is cl. Just ask the command prompt.Cases and points I say!
Last edited by MK27; 07-15-2009 at 10:55 AM.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
Learning everything at the same time is a formula for disaster.Yes, but while being confused by an IDE is no real cause for tears, wanting to be a computer programmer who doesn't use the command line sounds almost oxymoronic. They should be comfortable with CLI *before* they start programming IMO. And I bet if they were, they would not seem to have so much trouble with the IDE.
Ie, if you are a programmer, IMO the IDE is optional, but the command line is not. Sorry.
I don't think the "beginners" to which I referred are command line wizards who have been baffled by a set of drop down menus and a mouse, if you see my subjective opinion
Learn the language first (at least well enough to get past all the real beginner mistakes); then you can teach them how to write Makefiles...
But of course, I think before they even get into programming, they should take some OS courses including UNIX & Windows. Then they'll learn how to use the command line and how the OS works.
"I am probably the laziest programmer on the planet, a fact with which anyone who has ever seen my code will agree." - esbo, 11/15/2008
"the internet is a scary place to be thats why i dont use it much." - billet, 03/17/2010
No. The compiler is called Microsoft C/C++ Optimizing Compiler
Just run it on your command prompt.
cl.exe is just an executable name. Could be rocksolid.exe and should still say the truth. Meanwhile Visual C++ is the generic name given to the C/C++ component of the Visual Studio, including the IDE, compiler, linker, and libraries.
Anyways, I use visual C++ and MinGW on windows depending on what i'm doing, and gcc on Linux.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
But in all seriousness, those are not exactly easy things to do. They require vast amounts of knowledge and things. Not exactly what the average programmer would touch or think about.
Maybe except for the web, but then again, that might be a special area too... but then again, I don't think you need to know command-lines nevertheless, even for that. I have done PHP programming and I didn't need to know a lot of command-line stuff. Mostly just about variables.
In all seriousness, that comes from the eyes of a Linux user.All of those things are now going to be problematic for you if you have grown up ignoring the command line and therefore the fundamental basics of what an operating system *really* is (not what a particular OS ended up like on the surface).
What all operating systems have in common in the kernel.
The layer on top, the GUI layer changes from each operating system.
In Windows, it's all about UI, and in Linux, the focus is on command lines.
I definitely would not call command lines basics for an OS.
I can't agree with that either. Which OS came first or which kernel is used the most, or things like that, doesn't matter. It doesn't matter which OS has the biggest market share either.The "subjectiveness" of linux use is not a parallel to this at all, since while it may not be as widespread on home PC's, it is much more closely related to unix (almost a unix clone) meaning it has a much greater "heritage" in computer science generally. I'm not bashing MS or claiming that ultimately linux is better, just that the MS OS is more of an exception, whereas *nix should be considered "the rule".
An OS is an OS. Linux is no different or better than Windows. Just because it has a greater "heritage" doesn't mean it's "the rule". Nor is Windows "the exception". They are two different OSes, that's all. Neither approach is more right, and that means learning about Unix-like environments is not a prerequisite for a programmer IMO.
That's not fair. The main users of Linux aren't casual people, it's people who are into computers, geeks as some may call them. Of course they can use Windows, because just as with Linux, they know how computers work and have the desire to learn computers.Witness, this is not about linux users who can't use windows -- they can -- it is about windows users who can't use linux, presuming it is a minor sort of fad, as opposed to a limb of the real elephant, UNIX.
Take a casual user, make him/her learn Linux. Can he/she use Windows later? I doubt it. Seriously.
I would like to see that...One day in the future, programming may really become moving little icons around with your mouse. But we ain't there yet...
