Artur Grabowski <[EMAIL PROTECTED]> writes:
> "Gregg Reynolds" <[EMAIL PROTECTED]> 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
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 pa
"Gregg Reynolds" <[EMAIL PROTECTED]> 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 devel
On Tue, Mar 27, 2007 at 05:10:48AM +, [EMAIL PROTECTED] wrote:
> Has anyone played with OpenGrok yet?
http://opengrok.creo.hu/openbsd/
From: "Gregg Reynolds" <[EMAIL PROTECTED]>
>
> 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.
>
> I see GNU Global does something similar:
Has anyone played wit
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.
I see GNU Global does something similar:
http://www.tamacom.com/tour.html. Ever looked at it?
BTW I plan to write up a paper or guide on
Nope, I am a vim whore!
On Mon, Mar 26, 2007 at 05:55:48PM -0700, J.C. Roberts wrote:
> On Monday 26 March 2007 17:24, Marco Peereboom wrote:
> > ectags
> > ctags
> > cscope
> >
> > All work fine within emacsOS and vim.
> >
>
> Marco, are you running emacsOS on the SIMH PDP-8 emulator or did you
On 3/26/07, Tobias Ulmer <[EMAIL PROTECTED]> wrote:
lint(1), gcc-local(1)
style(7) may be worth reading...
Thank you; I didn't know about those man pages; I'll have to dig
around and find what other similar pages are there. OpenBSD's
documentation is pretty amazing.
-gregg
On 3/26/07, Nick ! <[EMAIL PROTECTED]> wrote:
OpenBSD... does not work like that. What made you decide it is a
"terrific development platform"? You do not even understand it's
philosophy.
I understand the Standard Response to that would be RTFM. But that
would be unhelpful, and even worse, ru
On Monday 26 March 2007 17:24, Marco Peereboom wrote:
> ectags
> ctags
> cscope
>
> All work fine within emacsOS and vim.
>
Marco, are you running emacsOS on the SIMH PDP-8 emulator or did you go
buy one of the original machines?
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 deve
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?
On Mon, Mar 26, 2007 at 01:27:46PM -0500, Gregg Reynolds 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
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]
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 (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been looking for static code analysis tools for a while, and the
only real free tools I've found are rats and flawfinder. The other
stuff is... not very useful. Either incomplete, reliant on non-free
parts, reliant on Java (not GNU
16 matches
Mail list logo