On 3/27/07, openbsd fan <[EMAIL PROTECTED]> wrote:
>
> pkg_ add vim-7.0.178-gtk2.tgz + vim plugin C/C++ IDE + vim plugin Perl IDE
> is what I use. Here is the website for the plugins:
>
> http://vim.sourceforge.net/account/profile.php?user_id=169
>
> Working with these vim plugins + Openbsd vim package is an absolute
> pleasure.
>
>
> On 3/26/07, Marco Peereboom < [EMAIL PROTECTED]> wrote:
> >
> > ectags
> > ctags
> > cscope
> >
> > All work fine within emacsOS and vim.
> >
> > http://fxr.watson.org/ is invaluable too.
> >
> > On Mon, Mar 26, 2007 at 02:16:49PM -0500, Gregg Reynolds wrote:
> > > 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?
> > >
> > > On 3/26/07, Gregg Reynolds <[EMAIL PROTECTED]> wrote:
> > > >Hi,
> > > >
> > > >I wonder if the OpenBSD developers have a favored set of tools for C
> > > >code analysis. E.g. the kind of stuff listed at
> > > >http://www.spinroot.com/static/. Esp. stuff like
> > > >http://spinroot.com/uno/. Are such tools used in OpenBSD code
> > audits?
> > > >
> > > >Also, what about automatic code documentation tools (for lack of a
> > > >better term)? This kind of stuff:
> > > > http://en.wikipedia.org/wiki/Comparison_of_documentation_generators.
> > > >
> > > >I'm interested because I think OpenBSD is a terrific development
> > > >platform, number one, and number two, I'd like to follow the code
> > > >development practices of OpenBSD.
> > > >
> > > >Thanks,
> > > >
> > > >Gregg
