Ugh. Comments like these are highly subjective, and we had a discussion about these before, and I am going to tell you that I 100% disagree. Command lines are evil, and so are make files. Make files are especially evil for small, easy projects.Originally Posted by medievalelks
This is all subjective, but then again, so is your opinion. An IDE is the best thing to do for a newbie.
What do you think an IDE is, except a pretty face on a make file?
Pretty faces are pretty - they hide the gruesome innards of things. I like pretty.
Then you should start programming in python or ruby. Those languages hide the gruesome innards which are exposed through C and C++. I think you would be much happier then.
bit∙hub [bit-huhb] n. A source and destination for information.
C++ hides the gruesome innards of C. No thank you.
Don't take the replies literally. I was just writing a way of saying "command line compiling is subjective; perhaps you shouldn't mention it to a newbie."
Couldn't disagree more. Why present a newbie with a dizzying array of buttons, menus, panes, etc. when you can teach them the basics of compiling with something as simple as "g++ main.cpp"? In .cpp program, out executable. Even better, show them how to compile and link separately.
Or do you like the ten questions we get a week asking why nothing came out of the back of the magic box when they pushed the "Build" button?
The OP's question isn't answered yet. Is it necessary to derail the thread on something so subjective?
The whole idea of opening a command window and typing some unfamiliar stuff (and that isn't an optional command line either) is pretty intimidating to me.
I mean, there is a reason why we use GUI instead of command line is all our electronic stuff, isn't there? I find myself having it easier to remember clicks (and being able to read what is in front of me) instead of scanning through a manual or lots of text to find the best way of doings things.
Come to think of it, I just had a course today on peoples' behavior. And it turns out that doing a lot of stuff prior to make something work just discourages people.
Saying "come in time" is not as likely to make people come in time as rewarding them when they do.
Ah, and I do so agree of Daved's reply. But as for the original post: I believe we are waiting for the OP to return with more information.
I believe it was answered. He downloaded and installed codeblocks-8.02-setup.exe instead of codeblocks-8.02mingw-setup.exe
bit∙hub [bit-huhb] n. A source and destination for information.
Actually, I think it was answered (need to configure the compiler in CB). And I don't really think I derailed the thread, I merely offered an alternative way to learn programming that would avoid the OP's problem altogether.
The problem was a misconfigured IDE. Or perhaps mis-installed.
It's the same as having a mis-configured compiler. Or mis-installed. I wouldn't separate those things as different problems at all. I think your way is just another way of compiling, not avoiding problems.
Compiling on the command line most certainly avoids problems with IDE configurations,and the need to learn an IDE before you really need one (if you ever really do).
You need to learn the compiler to use it, just as you need to learn the IDE. And learning a compiler is usually more difficult then to learn the basics of an IDE (I'm talking about human perception).
And I must point out that it is possible to incorrectly modify compiler configuration too.
They seem rather "weak" arguments to use that way, it seems to me.
It's another way, but I find it in no way superior to the IDE way.
And your web browser would be Yahoo...?
</sarcasm>
My homepage
Advice: Take only as directed - If symptoms persist, please see your debugger
Linus Torvalds: "But it clearly is the only right way. The fact that everybody else does it some other way only means that they are wrong"
>> I believe it was answered.
Ok, the last response I saw was "i have Code Blocks.." It didn't seem like the OP understood what to do next.
But as long as we're off topic, I think a simple IDE makes as much sense to start the user out with as command line coding (and certainly more than makefiles). I've seen plenty of people confused about the proper command line parameters to get a simple program to compile. The argument that we get 10 questions a week about IDEs doesn't mesh with my experience.
Setting up an IDE is rarely more difficult than setting up a compiler by itself. Configuring it is rarely that difficult either. Finding the buttons for build and run also is pretty simple. IMO, use the IDE for intro to programming, and then in the second or third course (or later in the intro course) require makefiles for completeness of instruction.
