Re: Next Gen JDEE

Beanshell in the current JDEE already does what I'm proposing we replace CEDET with Clojure/Cider + the "parse Java" API.  It wouldn't be an external tool; rather it would be an API we write clojure code glue code around.

On Jul 15, 2015, at 5:18 PM, Stephen Leake <[email protected]> wrote:

> Paul Landes <[email protected]> writes:
> 
>> Regarding CEDET: I can be convinced to use it, but my experience with
>> it (and trying to fix things during idle time etc) has been a little
>> negative. Another reason is it has to keep up with the changes of the
>> Java language. The idea is there are Java syntax parsing tools that
>> will keep up with the changes faster than sematic.
> 
> All such changes should be local to jdee2, mainly in the java.bnf and
> associated action code. Unless you find bugs/deficiencies in
> CEDET/Semantic, of course.
> 
> Merely using an external tool that can "parse Java" doesn't provide full
> Emacs integration.
> 
> 
> -- 
> -- Stephe
> 
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> jdee-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jdee-devel


------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/