RE: [ jEdit-users ] Broken search macros in 3.1final

[John G. <jge...@ny...>]

> --- Jeremy Wadsack <jwa...@wa...> wrote:
> >
> > > It would be nice to have a plug-in that would tell you the
> > dependencies within
> > > your project, so that you could easily know all the other
> > project members that
> > > call a certain part of the code. I'm imagining JBrowse,
> > parsing the entire
> > > project, with the ability to show "references" and
> > "referenced by" classes,
> > > methods, fields, macros, etc...
> >
> > How about javadoc? It's not a plugin, but it will tell you all
> > the
> > 'uses' and 'used by' for each method in every class it
> > documents (in a
> > session).
>
> The use and used by features of JavaDoc only document usage of
> Java types as argument of return types. If you use a method
> within another method, this is not documented by JavaDoc. The
> only tool that can show all the references, referenced by, etc.
> for Java code is IBM VisualAge for Java. VAJ has an incremental
> compiler whenever I save a piece of code. After every change I
> see directly if dependencies are broken.
> I like jEdit very much as an editor, but it can't compete
> against VAJ for my Java development.
>
> Ringo
>
> =====
> Ringo De Smet
> Email @ home: Rin...@bi...
> Email @ work: Rin...@bi...
>

Would VAJ be able to show broken depenedencies in non-project code like a
BeanShell macro, which isn't compiled and doesn't require explicit typing?
What if you adopted strict Java syntax for macros?

John