Re[2]: [jdt-core-dev] Analyzing class dependencies

[Marco Qualizza <mqualizza@xxxxxxxxxxxxx>]

I'm sorry, I couldn't help putting this through babelfish
(http://babelfish.altavista.com)... I think that some of your message
got garbled -- here's the result:

I made times sowas with GNU byte code - however as Kommandozeilentool,
that dependence out-spits and I believes also the cycles. If you which
helps, I can raussuchen the sources again. However nix next week ago
will become.

Now I need to learn German. :-)


> Hi,

> ich habe mal sowas mit GNU Bytecode gemacht - allerdings als
> Kommandozeilentool, das die Abhängigkeiten ausspuckt und ich glaube auch die Zyklen.  Wenn
> dir das was hilft, kann ich die Quellen nochmal raussuchen.  Wird aber nix vor
> nächster Woche werden.

> Ciao

> robert

>> > Jan,
>> > 
>> > the latest Eclipse build (I20030422) already contains a call graph
>> > view. So you might want to look at this before you start implementing
>> > your own. May be you can extend this one.
>> 
>> Dirk,
>> 
>> Thank you for the reply. I just checked the new "Call Hierarchy" view:
>> it appears like a stripped down version of dk.kamstruplinnet.callers,
>> which is a very useful plugin, but rather far from what I mean.
>> 
>> My plugin is intended to give a global view of dependencies between
>> classes and especially packages in an entire project, maybe compute
>> some metrics, maybe provide easy access to certain refactorings.
>> 
>> > Are you aware of the org.eclipse.jdt.core.dom package? It contains
>> > public classes to build an AST for a compilation unit, so there is no
>> > need to hack the internal compiler to achieve your goals.
>> 
>> Yes, I tried to use those classes. Parsing a compilation unit and
>> resolving type bindings through this API takes upwards of 500 ms.
>> Achieving the same result in a batch compilation takes 14 ms per
>> compilation unit. I don't know why the difference is so huge.
>> 
>> > The mailing lists are reserved for discussions about evolving Eclips
>> > itself. User questions like yours are better posted to the news group
>> > eclipse.tools.jdt.
>> 
>> Ok - I thought my concerns might be closer to the "core" than to
>> the user interface (see also my other email about package scopes).
>> But I will ask on eclipse.tools.jdt next time.
>> 
>> Best regards -
>> Jan Ploski
>> 
>> _______________________________________________
>> jdt-core-dev mailing list
>> jdt-core-dev@xxxxxxxxxxx
>> http://dev.eclipse.org/mailman/listinfo/jdt-core-dev
>> 



-- 
     "The very existence of flamethrowers proves that some time,
      somewhere, someone said to themselves, 'You know, I want to set
      those people over there on fire, but I'm just not close enough
      to get the job done.'"
         - George Carlin

    Insurance-Engine.
    (613) 234-2426x226