Hi folks,
I don't know if everyone has seen the proposal below. This
seems to have some intersection with what we've discussed in the past
(compiled-languages common layer, Wind's proposal from last EclipseCon, etc). I
think members from CDT should be involved (at least provide some input) --
if people are interested, I can set up a meeting with the LDT folks at
EclipseCon.
Sebastien
As per the Eclipse
Development Process, we are notifying the Eclipse Membership-at-Large of
the intent of BEA to propose the Language
Development Toolkit Project as a Technology sub-project. A brief description
of the project is below. A draft project proposal is at http://www.eclipse.org/proposals/eclipse-ldt/index.html
Language Development Toolkit The
proposed LDT project would extend the success of the JDT to a more general
concept of language aware services within the Eclipse framework, increasing
the degree of reuse among language-enabled editors and views while decreasing
the costs of implementing new languages and language services. Steps toward
this goal include extending the JDT to support metadata-driven programming
(“apt/mirror”), defining public APIs to support languages that contain nested
Java regions (JSP, BPELJ), and increasing support for cross language
translation (Schema-to-Java bindings, IDL compilation, Ant task debugging, and
so forth), including generalizing the Java project model to additional
languages. Long term goals include moving toward a common source editing
framework parameterized by language analyzers (lexers, parsers, and checkers)
rather than independent silos that recreate base functionality. LDT provides a
collaborative arena for developing such concepts and a staging ground for
integrating them with established areas of Eclipse, including the JDT, SSE,
CDT, and others.
We look forward
to input and discussion from the Eclipse community.
|