Hi Marcus, That type of clean up is currently being worked on for wtp 3.2.
Thanks,
Chris
Marcus Better
<[email protected]
> To
Sent by: [email protected]
wtp-dev-boun...@e cc
clipse.org
Subject
[wtp-dev] Re: JSDT status?
06/08/2009 07:28
AM
Please respond to
"General
discussion of
project-wide or
architectural
issues."
<wtp-...@eclipse.
org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Nitin Dahyabhai wrote:
> JSDT's JDT ancestry allows for anyone to supply a completion "computer"
by
> extension point (org.eclipse.wst.jsdt.ui.javaCompletionProposalComputer),
> and provides mechanisms for accessing and modifying our AST (it mirrors
> the JDT constructs, but is too much to detail here).
Incidentally while implementing an inference engine for JSDT (mostly
experimental) I noticed several pieces of code and interfaces that seemed
to
be inherited from Java but are not meaningful for JavaScript. Is there a
plan to remove such code to reduce clutter? Should I file bugs? What about
names like "javaCompletionProposalComputer"?
Cheers,
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkos9eAACgkQXjXn6TzcAQkurACg0ZqBh7otoNUPyfaXu+L52TES
JOEAoI1cajy+s9LGruAKo+X+YMnfWIlW
=t8DF
-----END PGP SIGNATURE-----
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
<<inline: graycol.gif>>
<<inline: pic03174.gif>>
<<inline: ecblank.gif>>
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
