Wow that is a lot nicer on the eyes Mario... Thanks for the tip.
Wow that is a lot nicer on the eyes Mario... Thanks for the tip.
Not Code::Blocks, but I prefer a lighter background -- being neither a fan of white nor black.
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
Sorry for the off-topic... but do you use SlickEdit with GCC, dave? How do you feel about the integration with this compiler? But particularly the gdb?
I had it evaluated twice. I emailed them and asked for a an extension because at that time I ended up by not fully evaluating it. Stupidly enough I finished doing the exact same thing when they so kindly extended it for 5 more days. I don't have the nerve to ask them again. But was very impressed at most of its features. Sadly I didn't fully evaluate the compiler integration.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
Not professionally, but...Originally Posted by Mario F.
I just got v11 today, so I'm still forming an opinion -- v7 was not so great.Originally Posted by Mario F.
I grabbed the latest eval, which ran out. At the same time I had been using CodeWright 7.5 or something and the vendor-necessary IDE (all at the same time). After a frustrating week or so of missing several features, I went to the higher-ups who approved my request.Originally Posted by Mario F.
...Officially I don't use GCC at work -- although I've had real interest as of today to try to write a very quick-and-dirty communicate-through-the-serial-port thingy. My first attempt to use gdb I was surprised that it actually had gdb as part of SlickEdit, but it did not work correctly. And I looked into it only for that minute. Other than that, it pleasantly did things I wasn't expecting.
It may just be a setup issue (in part because I choose not to put a lot of junk in my path, but to instead call exe's direct).
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
Yes. I noticed is that the compiler/debugger setup is complex. This may be a sign of fully or near fully integration. The person I spoke with from their offices (they actually phone you home. expect a call soon), guaranteed nearly full integration with GCC. A selling POV maybe. But he seemed honest enough about it.
I did notice the debug menu in slickedit (one the first places I go on any editor... for any language). It blew me away considering other IDEs with gcc in mind. It supports conditional breakpoints, watchpoints, multi-threading debugging... I don't think it does catchpoints and tracepoints although he did tell me it does partially support catchpoints through the breakpoint toolbar. But the question about tracepoints remained unanswered.
Needless to say the editor features alone sell it. Albeit a little hard to get used to. Some of the concepts, if not new, are definitely not common.
Anyways... thanks. At $280 USD for a single-user license it poses a dilema. I've felt through this learning experience of mine that gcc/gdb UI integration is lacking in windows. And here it is what seemed to me at a glance the best I've seen so far.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
DIFFzilla (which I've used for several non-code searches -- like modified jpg's -- as well) and its own incremental backups (love that!) made up for my version control failings -- that was my kicker. (Besides Ctrl+/ and Ctrl+..)Originally Posted by Mario F.
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
thanks for the theme, but what's a nightly build?
Last edited by indigo0086; 09-20-2006 at 10:28 AM.
Ah! There's a lot more to Code::Blocks than the version you have right now, Indigo.
It's in development and they throw a Nightly Build version every day with many improvements over the RC1 you are using.
http://forums.codeblocks.org/index.php?board=20.0
read the stickies before anything else.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
I'm going to download Code::Blocks. After reading around the website it seems more featureful than VS 2003.
EDIT: And I may even start using MinGW
Last edited by cboard_member; 09-20-2006 at 12:43 PM.
Good class architecture is not like a Swiss Army Knife; it should be more like a well balanced throwing knife.
- Mike McShaffry
I see, I didn't bother because I thought I wouldn't need it.Originally Posted by Mario F.
Please forgive the OT bump, but I did get resolution to my issue.Originally Posted by Mario F.
http://community.slickedit.com/index.php?topic=458.0
[Registration apparently required to see the posted attechments.]
It worked quite well after a fairly easy fix -- but I didn't jump too far into specifics of debugger operation.
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
Thanks Dave. I have MinGW separately installed from the editors and using GDB 6.3. Didn't ran across that problem back then. Don't know why. Maybe because I did change the debugger during first-run setup.
I've emailed them yesterday and told them of my decision to buy. But did ask for a couple of days evaluation... again to set the score right about the debugger integration. My guess is that I will be happily impressed. Nothing impressed me unfavorably on slickedit so far.
Waiting for a reply.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
hello,
sorry for reviving this topic, but it found it looking in google for some solution to my problem.
i am using a black background in codeblocks, changing the default color on highlight syntax menu tab.
my problem is that i cannot see the cursor, small detail but critical
im on a mac, and i searched inside the folders for some file *.conf but havent found any.
any help is welcome
My IDE: