Artur Grabowski <art@blahonga.org> writes:

quoted text
> "Gregg Reynolds" <dev@mobileink.com> writes:
> 
> > Clarification:  I'm mostly interested in source browser tools (e.g.
> > cscope, e/t/gtags, global, etc.) or whatever can help a developer
> > understand unfamiliar source code in the shortest possible time.  Is
> > there a preferred tool among OpenBSD developers?
> 
> less(1), mg(1), eyes, keyboard.

To expand on this. I've noticed that the more someone depends on
syntax highlighting, automagic jumping to functions, auto-completion
in editors, etc. the less he actually reads and works with the
code. Tools remove you one step from the code and make you less
intimate with it.

Tools that help you read software is like eating Viagra and installing
an auto-humping device in your bed. Sure it makes things easier, but
you'll be missing quite a lot of important stuff that way.

I do use code viagra occasionally (my favourite brand is id-utils),
when doing large sweeps of the code to change the same thing over and
over, but never when doing something creative.

//art