Wouter van Ooijen wrote:

>> Compiler errors are not a replacement for linting. Use a linter and a
>> highlighting source editor (I assume you already do that).
> 
> I never used a linter, and I mostly use simple text editors. 

I'm not sure how simple is simple for you, but IMO one can gain a lot of
productivity with a good editor. There are a few decent free ones out
there, and also a few not so expensive ones. For whoever makes his living
(or part of it) with coding, spending even a few hundred USD on an editor
that helps save an hour a week is a very good investment.

Syntax highlighting I consider a very basic minimum for a source code
editor. Some means to display and jump to the definition and/or declaration
of a symbol is also important. Knowing the symbols in my symbol universe
(depending on the scope) and suggesting appropriate ones helps reduce
typing a lot and makes using meaningful names much easier. Code folding
helps with keeping the big picture in the eye. A regex-based grep-style
search and replace that can work over files in an editor project can be
quite useful (as editor projects). Project setups that can be stored in
editor config files make it easier to just jump into a project that I've
worked on months or years ago, and be right back in the setup I used when
working on it -- even if it's in a language that I haven't used since.

Gerhard

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