[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ide-dev] Eclipse Languages Symposium
- From: Andrew Eisenberg <andrew@xxxxxxxxxxxx>
- Date: Sat, 24 Aug 2013 20:55:15 -0700
- Delivered-to: firstname.lastname@example.org
I added a comment to https://bugs.eclipse.org/bugs/show_bug.cgi?id=415563
, but thought that maybe I could get some more discussion here. Frankly, the idea of rewriting JDT or any mature *DT scares me. It is too late to do that and there will be lots of wasted time just to get back to where we started from.
The idea of a common language infrastructure has value and is potentially doable. Perhaps providing some extension points and a bit of infrastructure that enables *DTs to interoperate and communicate would provide some nice incremental benefits. I'm thinking in particular of features like search, navigation, content assist, and refactoring (particularly across JVM languages). This infrastructure would have to sit on top of JDT (or next to it) and would have to be opt in for each *DT. But, something like the common navigator, which is fairly successful (despite some rough edges) shows that this kind of integration is possible.