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
-
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 :doh: 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.
-
Chris is right - and it isn't even just software. A couple of times I have had problems with complex hardware prototypes not working - until you put an oscilloscope probe in the right place to monitor what the software is doing to it, and the problem goes away... That, my friend is when the nightmares start.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
The boy is already trouble with CPP and you are threatening him with oscilloscope :laugh: How about forgetting to connect your circuit board with ground and your embedded device is not running at all :sigh:
-
Ouch buddy, you don't even know what are you talking about :doh: 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
-
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
-
The boy is already trouble with CPP and you are threatening him with oscilloscope :laugh: How about forgetting to connect your circuit board with ground and your embedded device is not running at all :sigh:
-
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
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.
-
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.
-
Too simple. How can you overlook that you have no power at all?
At least artificial intelligence already is superior to natural stupidity
do you think i spent all day? not at all, i found it right away. but can i blame micro-controller for this?
-
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
-
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 againSounds 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
-
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 againSounds 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
-
a price that you wont notice on core i processors
-
a price that you wont notice on core i processors
-
When i was beggining to make some programs i had to make a small ellectronic book in c++. It started ok, i managed to make a reader and an editor and then came the worst error a programmer can have. When I compiled the program it went smoothly but when i openned it from windows it showed and internal error message whit no message. I suspected it was an I/O error because when i copied the program to c: or d: didnt showed the error but when i placed in other folder that wasnt the root it showed the error message
-
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?
That's happened to me a few times (occasionally with C++ Builder too!). In each case it has been a variation on: Different memory (especially heap space) allocations between the debug and live environment (even on the same machine). Debugger initialising memory to something sensible, thus hiding an uninitialised variable somewhere in my code, debugger locating the program in a different area of physical memory, thus avoiding a faulty patch of RAM that - by coincidence - wasn't used by the OS normally either, and so on In other words, this type of problem is almost always memory related in some way, or possibly due to uninitialised use of a physical device or internal queue in some that way the debugger covers up when it sets up the debug environment. One technique that can sometimes help catch this is to use a remote debugging session run from a second machine - often the remote debug stub will not do as much pre-execution setup as an integrated debugger, thus leaving the problem undisturbed, or at least different. I remember one particular problem porting a program from C++ builder to Linux, where the C++ Builder program loader initialised class memory to 0 before starting the program, whereas GNU C++ didn't - took me a while to spot that, as the program only failed when loaded without gdb (which placed it in an area of memory that was, by chance, all 0s!) Oh, happy days... 8)
-
do you think i spent all day? not at all, i found it right away. but can i blame micro-controller for this?
-
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
Please, please, please stick to C# programming. It sounds like you're not cut out for C++ development.
-
the ide was c++ builder 6
Not really a C++ myself but I was under the impression Borland Builders were one the best. I was under the impression that the Microsoft versions were created and then Microsoft created the standards to fit, my experience of VC++ is you type a quick test program spend an age trying to figure out why it wont compile, get fed up use Builder6 load the code press F9 away you go!
-
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++
Vasily Tserekh wrote:
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++
You "hate" C++ because you don't understand it. To be clear, in .NET languages like C# and VB.NET (and similarly in Java), when there is a unhandled fault, the end user is presented with a exception that includes a stack trace. Generally you would never want a end-user to see a stack-trace. You can get exactly the same thing in C++ if you choose to, but it requires additional work that is done for you in a managed environment. Generally stack traces are available in a debugger.
/* Charles Oppermann */ http://weblogs.asp.net/chuckop
