From: Joshua Branson <jbranso@fastmail.com>
To: emacs-devel@gnu.org
Subject: Re: Current State of CEDET in Emacs tree and standalone
Date: Thu, 19 Jul 2018 10:48:32 -0400 [thread overview]
Message-ID: <87601b9t8f.fsf@fastmail.com> (raw)
In-Reply-To: <CADq4APu4P=hnPkhWeMEF737x+pG6drqEAupa9TdCom1K3VkoFA@mail.gmail.com> (Andreas Marschke's message of "Tue, 10 Jul 2018 15:09:12 +0200")
Andreas Marschke <andreas.marschke@gmail.com> writes:
> Hi all!
>
> In a quest to add some improvements to CEDET/Semantic I came across the fact of the splintered codebases people are potentially working on.
>
> We have the CEDET project on SourceForge with changes going beyond the initial import into emacs.
> And then there is the version shipped with Emacs.
>
> When comparing the code basis one of the most immediate things that struck me, was the availability of tests and that there was even rudimentary unit testing employed, This is not the case
> for the code in Emacs tree.
>
> Are there efforts to import the code from Sourceforge anew into the emacs tree or is it intended to remain there as it pertains to features not intended to be shipped with Emacs?
>
Not to be a debbie downer, but is CEDIT worthwhile to continue?
(admittedly I really don't know much about CEDIT). I'm under the
impression that semantic may not be needed, since microsoft is pushing
the LSP (language server protocal).
Just curious,
Joshua
next prev parent reply other threads:[~2018-07-19 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 13:09 Current State of CEDET in Emacs tree and standalone Andreas Marschke
2018-07-10 13:42 ` Noam Postavsky
2018-07-19 14:48 ` Joshua Branson [this message]
2018-07-19 20:58 ` Andreas Marschke
2018-07-20 15:38 ` Joshua Branson
2018-07-20 2:26 ` Richard Stallman
2018-07-20 15:40 ` Joshua Branson
2018-07-20 16:12 ` João Távora
2018-07-22 2:14 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87601b9t8f.fsf@fastmail.com \
--to=jbranso@fastmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).