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)? Just because it doesn't come out of the box with
whatever compiler you installed doesn't mean it's not there. This is not
related to C, this is related to lack of doing what a programmer needs
to do.

OK.
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, and you have what could be
consdiered to be a new flavour of the language (especially if you squint
your eyes when you look). If a better language is one which doesn't ley you
do bad things and enforces the doing of 'good' things and C doesn't do that
then this MUST be a new language. Right ? ;-).

Sounds suspiciously like Delphi :-)

You could even add Olin's? cotton-wool can't-user-redefine-instructions as
an optional switch. Sounds a surprisingly 'nanny-state'  approach for Olin
to be advocating, but would have it's advantages)(As long as you can turn it
off :-) ).



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