|
Not sure what you're saying exactly, but one of the worst things IMHO, that a programmer can think is that program compilation has anything to do with program operation.
|
|
|
|
|
yes i know that but imagine that you cant trace an error because when you debug the executable it doesnt show up,
what would you do?
|
|
|
|
|
Usually that means that there are environmental differences between your DEBUG running and the running that produces the errors. You need to figure out how to isolate these differences and determine why they are the cause of the error. Sometimes the addition of a logfile to write entries to, can help you narrow down the code that is failing.
Oh and this isn't something that just happens to C++. It can happen with other languages too. 
Chris Meech
I am Canadian. [heard in a local bar]
In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
|
|
|
|
|
yes I know but at least in managed languages you get a nice error message not a blank error messsage, thats why I hate c++
|
|
|
|
|
And what if that useless message comes out of some library or DLL you are using? How is C++ responsible for that?
One thing is almost certain: You have some unclean code somewhere in there which you get away with in a debug build, but not in a release build. Like it or not, but you are going to have to find that code and then fix it.
At least artificial intelligence already is superior to natural stupidity
|
|
|
|
|
there is no release and no debug, just a regular .exe that when is run from the IDE to debug it goes fine, but when you click it on windows it goes wrong
|
|
|
|
|
Ouch buddy, you don't even know what are you talking about 
It must have to be either debug version or release version. as CDP1802 says, clean your code and stop complaining. and also try to figure out what is the differences and what is missing.
|
|
|
|
|
I surely know what i am talking about, HOW TO CLEAN A CODE THAT YOU CANT DEBUG. and surely you have ever worked with c++ builder 6, c++ builder doesnt have a debug and release version it only has a single output, instead of giving new ideas you talk about how good you are and how ignorant i am.
I will make it simple so your mind can understand!!!
step one -you write code
step two -you compile that code
step tree your ide launches the .exe and you try it
step four you test your program and i does just fine
step five you go to the application folder and make double click on the executable
step six the application show and erro message with no error at all
now you get it, how CAN YOU ISOLATE THE PROBLEM and when you isolate it what will you do if you can trace what is wrong
|
|
|
|
|
Step 7a: Read the code and try to locate the problem by analysis
Step 7b: (only if 7a fails) Try to shorten the code to rule out as much of it as possible as source of the problem
Step 7c: Identify potentially problematic code in what is left over and monitor it by logging
Step 7d: Draw conclusions from the logged values, go back to 7b if the results are not conclusive
Step 8: Fix the problem
Step 9: Restore all the code that has been commented out during troubleshooting
And now repeat 500 times 'I WILL NOT SHOUT AT THOSE WHO TRY TO HELP ME'.
Edit: And there is also the tiny possibility that the compiler is a little antiquated and has a little problem with newer windows versions.
Edit^2: Borland C++ Builder is from 2002. 10 years old, meaning it's probably a rare item in computer museums
At least artificial intelligence already is superior to natural stupidity
modified 25-Apr-12 10:20am.
|
|
|
|
|
Thanks for brightening up my morning! Such things make me
|
|
|
|
|
Everybody hold on one minute and take a deep breath. True: the HoS is not for questions. So look closely at the title of this thread and the original post. Vasily did not ask a question, he told a story from long ago (C++ builder 6 came out in 2002) when he was "beginning to make some programs" and ended up hating C++. He was not asking for help, and he reasonably responded to unsolicited advice by reasserting his reasons for hating C++. You may not share or understand the bad taste the experience left in his mouth, but do not slam his competence (he was a beginner ten years ago, remember?) and drag him into a screaming match then bitch-slap him for getting frusterated.
Get a GRIP.
Now...
I learned to program as a kid in the early 80's and was good at it until I tried to learn OOP and windows programming simultaneously without a teacher, using Borland OWL on Win3.1. With no internet. The documentation was...terse. My code was corrupting the bitmaps used for drawing the minimize/maximize/close buttons. My code crashed. Then my code crashed WINDOWS and dumped out to the command prompt. Not kidding. Bad taste in mouth. For Windows, lParam, wParam, C++, Borland, the whole mess. It was definately HoS experience. I still hate C++ on a deep emotional level that will not be mollified by any appeal to reason. Today I program command line apps in ANSI C and couldn't be happier.
|
|
|
|
|
great, at least someone got my message, a lot of great programmers had their bad days with c++ at least i was lucky to live in a time were you have plenty other options, i was only geting out an old frustration and everyone that didnt had a bad time with c++ cant call himself a good programmer
exegetor wrote: I still hate C++ on a deep emotional level that will not be mollified by any appeal to reason.
I really enjoyed that quote it made me laught
|
|
|
|
|
You're a good person! 
|
|
|
|
|
http://fbe.am/5JO[^]
here is the software i found it i will give a million dollar to the brainy to tell me whats wrong
|
|
|
|
|
"here is the software"
file has a virus
|
|
|
|
|
C compilers have had release/debug, or flags you can set with the same effect (e.g. optimise on/off, inlining, etc) for a very long time.
You are not talking to people in a way that will get answers, particularly after posting in the wrong forum (the HoS is explicitly not for asking questions).
When I have fun like this I usually put lots of debug-to-console (or, if you are not running somewhere you can see that, to file) statements in and play divide-and-conquer to pin down where the problem is.
|
|
|
|
|
He mentioned using C++ Builder 6, which is 10 years old. It may very well be that its runtime libraries or the Platform SDK are simply antiquated.
At least artificial intelligence already is superior to natural stupidity
|
|
|
|
|
hello, thanks for the help but that was five years ago that was the ultimate reason to select C# as main language, I have not any plans to fix that code i dont need it. Now i remember the error message: a popup window with this: external exception and no more, somewhat i located the error message in a simply i/o read but i couldnt do anything because the SAME code worked in other projects and I wasnt able to tell what was wrong i had to drop the project.
now c++ fans how many times where you stucked because an error that have you haunted for weeks- a LOT
since i use c# i never ever had an uncomprehensive stupid error again
and please this is not a question forum i post it here to see if anyone had that kind of error once in their lives to feel that i am not alone
|
|
|
|
|
Vasily Tserekh wrote: now c++ fans how many times where you stucked because an error that have you
haunted for weeks- a LOT
since i use c# i never ever had an uncomprehensive
stupid error again
Sounds like a case of selective perception to me. I would also like to have that version of the .Net framework that never does strange things 
C++ has two faces. It allows low level programming close to the computer's hardware, down to supporting writing assembly directly. On the other side it allows to go to a very high level, not dissimilar from what you do in C#. What makes C++ so scary? It can't be strange behavior, because you will encounter that in some form everywhere. C++ libraries are not perfect and the .Net framework also is not. The scary part must actually be low level programming where you must know what you are doing but also get very fine control over what's going on in return. Don't you know that the nice safe .Net world has a price?
At least artificial intelligence already is superior to natural stupidity
|
|
|
|
|
a price that you wont notice on core i processors
|
|
|
|
|
*sigh* I knew he would say that...
At least artificial intelligence already is superior to natural stupidity
|
|
|
|
|
I don't know who this "you" is, but it isn't me.
|
|
|
|
|
In case you didn't realize: the reason Vista was so bad was that it was mostly programmed in C#. The result was a shabby, unstable, and unreliable system that was unusable to thousands of users all over the world.
The reason Windows 7 is a lot more stable is that MS reprogrammed much of the OS in C++.
Also, the error message you got most certainly wasn't related to what programming language you used. If you had done the same in C#, most likely the only difference would have been that you might have been given a hunch of what library or subsystem was at fault. A short question on a user forum like this likely would have provided you with the means of that same info as well, and on top of that with some advice how to fix it.
You had an unlucky experience at a time when you were experimenting with C++, but that doesn't mean that C++ at fault anymore than your car manufacturer is at fault when a meteor hits your car.
|
|
|
|
|
Do you only develop for yourself? Saying that performance is fine on YOUR computer doesn't mean it's good for your users.
Also, no I've never been stuck for weeks on a problem with C++ code... I've been stuck getting libraries to work (opengl, sfml, etc) but I know how to properly debug... In fact if you are hiding behind C# instead of learning to debug with unmanged languages, you are hurting yourself in the long run... Those skills are relevent in all languages and will help you the next time C# throws you a fancy error message that you can't make heads or tales of.
|
|
|
|
|
Stephen Dycus wrote: Those skills are relevent in all languages and will help you the next time C#
throws you a fancy error message that you can't make heads or tales of.
You are so right, but he is not interested in hearing that. When that day comes, he will treat us to yet another rant with the title 'That's why i hate c#'.
At least artificial intelligence already is superior to natural stupidity
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
