From: Zorro <hz...@gm...> - 2010-02-21 15:02:13
|
Tor Lillqvist wrote: >> However no error/debugging information was written to >> 'std::cerr'/'std::cout'. >> > Or more correctly, it was written, but those C++ streams weren't > connected to anything, so nothing showed up anywhere, especially not > in the console, from which you presumably started the program? If you > would have redirected the program's standard output and standard error > to a file (or piped them to "more" for instance), your would have seen > the debug information. > Indeed I did start my program from a console and didn't see any information written to the console. >> After finding my mistake using '-m windows' instead of '-m console' in >> the makefile I did a rebuild of my application and noticed it had become >> several magnitudes slower! >> > > Is the "console" exectuable writing debugging information that indeed > shows up on the console, while the "windows" executable just tries to > write such information but it doesn't show up anywhere? Isn't the > reason for the perceived speed difference then clearly that it's the > output to the console window, including scrolling it, that is slowing > the "console" program down? > No! When calling my program without parameters it would write a 'Usage: ...' line to the console or when calling it with erroneous parameters it would write an error message to the console. > What happens if you redirect the standard output and error of both > executables to a file? Do you still see a speed difference? > No then I do see (as expected) the same speed difference! Btw thnx for reacting. Harm-Jan Zwinderman |