Russell McMahon wrote:
> Most of these errors are due to insufficient programming environments.
> How many people still program without syntax highlighting? Without
> autocompletion? Without an editor that scans your sources while you're
> writing and knows all the symbols and their scope? Without something
> like lint that would catch 99% of these silly mistakes (independently of
> the fact that most of them were already avoided by using a more
> appropriate editor)?

Yes, yes, yes, yes. And I do want to keep it that way! Syntax 
highlighting shows me what I already know and distracts me from what I 
should see. Autocompletion is at best useless for me, worst it gets in 
the way. I tend to know about symbols and scope, thank you. Lint might 
be an idea, but I tend to make gross blunders, not silly mistakes. And 
most C source I 'make' is actually written by Python code. Which of 
bcourse gives the Python syntax coloring a bad day.

There are one or two editor-helps that I do like, foremost showing the 
paired brackets, {}, (), begin-end, etc.

> So take the best in class of the support material, build it all into an
> integrated development environment so it's always there unless somebody
> explicitly turns some or all of it off

default to off, please?

-- 

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist