How do you rate the QB IDE?

[Hard Rock]

Bloodsheed Dev C++

I was going to say "1 word" but i dont think it really one word.. maybe it is anyways heres all i have to say:

memory leaks

[_Bill_]

You use Bloodshed to red? I think it has a pretty good IDE but Hard Rock I don't get any memory leaks with it. If I ever do get a Memory leak I use FreeRam http://www.yourwaresolutions.com

[na_th_an]

QB IDE is very comfortable, but it is a memory-hog. That's a pitty that when your project becomes bigger and bigger you have to abandon such a wonderful ide...

[LooseCaboose]

I still think you are all being too forgiving to the beloved QB IDE. It has some serious shortcomings and the case correction and syntax checking are nothing special and handled by a number of modern IDEs.

IMHO syntax highlighting is a must, maybe not so much for QB but it is handy when you are doing real messy C coding. Vi and emacs both had syntax highlighting very early on (vi at least was around in the 70's). I have also used 16 color syntax highlighting in xemacs at a console and it aint so bad, sorry Toonski ;-). The best trick I have seen with syntax highlighting was highlighting of HTML, with the comments having LaTeX highlighting :-).

The biggest problems with the QB IDE (IMHO) are the lack of code indentation (ie typing END IF should auto backspace the line), no paren matching (highlighting begin paren, when typing a close paren, helps prevent mismatches) and of course the memory problems.

My lesser differences with the humble QB IDE include lack of regular expression searching (grep), no shell access and lack of shortcut keys (the mouse just gives you rsi/oos/whatever).

Anyway, If it works for you, use it. :bounce:

[toonski84]

i still dont see the big screaming deal with syntax highlighting. you say it's a must, but it isnt. i do most of my coding in notepad, and i program c, basic and perl. i can differenciate stuff without it.

ps. what other ides have case correction and syntax checking? i've never heard of many...

[wildcard]

I agree with Toonski, I find syntax colour highlighting no so useful. Distracting actually.. I prefer CASE matching and also the immediate section in the IDE(very useful).

[red_Marvin]

yeah an the fact of it's "real time space controlling"

Code:

z= x     +               y

is changed to

z = x + y

that makes the code more readable...

[wildcard]

yeah an the fact of it's "real time space controlling"

z= x + y

is changed to

z = x + y

that makes the code more readable...

#

Much more readable, those space changes/additions really add up and help me tons.

[wizardlife]

After using the TP7 IDE, I'd have to say that my ideal IDE would have the multiple file option and simple syntax colouring of tp7 and the space correction and capitalization (except I'd prefer lowercasing) of QB's.

Actually, the Visual Basic 5.0 interface represents all of those features... I simply detest the language. The box should say 'Database Programming for Retards' on it.


I don't like excessive syntax colouring, but having the keywords highlighted a different colour from everything else is nice. Ex:

const myarraymax = 10

dim myarray(1 to myarraymax)
for a = 1 to myarraymax step 2
print "this is item #" + str$(a)
next

Here only the compiler keywords are highlighted. Print is only a statement, and str$ is a function.

[toonski84]

const myarraymax = 10

dim myarray(1 to myarraymax)
for a = 1 to myarraymax step 2
print "this is item #" + str$(a)
next

... is the code any less readable? actually, do any have auto-indentation? that *that* would be cool.