File I/O problem

Pages: 12
Thanks,anyway :)
Then I will stick with plain c++ for a while.
Hey, I've downloaded the latest wxDev here: http://wxdsgn.sourceforge.net/
good news, the IDE's been updated (Feb 2010)
bad news, the bundled compiler is old -gcc 3.4.5 (mingw vista special r3!)
I'm not sure how to this in wxDev, but try to upgrade your mingw-gcc, and yes, the compiled code behaved exactly like you describe it (I'm gonna remove wxDev now ;)

edit: here's how you can try to update your GCC:
http://stackoverflow.com/questions/1151420/mingw-update-gcc-version-3-4-5-to-version-4-4
Last edited on
I am not sure why anyone would use devC++. Sure, the wxDev version works a bit better than the original, but it still pales in comparison with other IDE's.
Thanks for the link matsom.I will try to update GCC.
Unfortunately Im spending half of my time to learn C++,and other half for solving IDE related problems :S As was the case in this problem.

hanst, I was going to switch from devc++ to codewarrior,but because of builtin wxwidgets designer&support in it and their same appearance made me feel comfortable with it.

hanst, I was going to switch from devc++ to codewarrior,but because of builtin wxwidgets designer&support in it and their same appearance made me feel comfortable with it.


Code::Blocks has the same thing with the wxSmith plugin, with the difference that Code::Blocks is better.
Oops,I wrote codewarrior.Maybe I should sleep.
LOL, if you want to try C::B, then try this, download only the IDE and get mingw-gcc installer from http://www.mingw.org/, install it first then install C::B -if you're the adventurous type, get the nightly builds ;)

iirc the setup steps I did was: install mingw-gcc using the mingw-get app (caution: the default only install the C compiler -must RTFM), add it to the windows path, then install C::B, the compiler detection was automatic, if you're dead set on using wxWidgets, you need to download it too and set it up to be used in C::B. Good luck.

p/s of course you can stay with wxDev, just follow the advice you got from the previous page, i.e do not use non-standard techniques when dealing with file i/o or general C++ programming (iirc the one you used was C style programming -struct+file i/o)

how the heck does this thread reduced to this discussion I don't know, sorry!
Topic archived. No new replies allowed.
Pages: 12