all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Tom Tromey <tromey@redhat.com>, emacs-devel@gnu.org
Subject: Re: CEDET merge question
Date: Tue, 08 Sep 2009 10:11:01 +0200	[thread overview]
Message-ID: <m3zl95svoq.fsf@verona.se> (raw)
In-Reply-To: <87eiql2w5s.fsf@cyd.mit.edu> (Chong Yidong's message of "Sat, 05 Sep 2009 12:28:31 -0400")

Chong Yidong <cyd@stupidchicken.com> writes:

> I have a question about CEDET that hopefully someone on this list, who
> has more experience using CEDET than me, can help answer (I've been
> corresponding with Eric Ludlam, but he's gone on vacation).
>
> The Semantic parser appears to have two major "back-ends", bovine and
> wisent, which are used to generate Semantic tags.  Does anyone know how
> crucial these packages are, and whether one or the other (or both) be
> dropped or somehow trimmed down?
>
> I ask because the CEDET merge already involves an uncomfortably large
> amount of code, and it's rather dismaying to see these two big code
> trees "embedded" in subdirectories of Semantic.  (Wisent, for instance,
> appears to be an entire Elisp reimplementation of Bison...)
>

Emacs hackers would still need easy access to these tools. Maybe this is
a further case for including something like Tom Tromeys ELPA in Emacs?
If we had something like that by default it wouldnt be a big deal to
distribute tools like these to Emacs hackers.



>
> (The CVS branch I'm using for the CEDET merge is not yet suitable for
> general testing; I'll inform the list when it's ready.)
>
-- 
Joakim Verona




  parent reply	other threads:[~2009-09-08  8:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05 16:28 CEDET merge question Chong Yidong
2009-09-05 17:22 ` David Engster
2009-09-05 20:53   ` Chong Yidong
2009-09-05 23:08     ` David Engster
2009-09-06 15:37 ` Richard Stallman
2009-09-06 17:46   ` Ken Raeburn
2009-09-06 21:11     ` David Engster
2009-09-06 22:26       ` Ken Raeburn
2009-09-07 13:33       ` Richard Stallman
2009-09-12 12:49         ` Eric M. Ludlam
2009-09-12 13:37           ` Miles Bader
2009-09-13 16:39             ` Richard Stallman
2009-09-14 11:22               ` tomas
2009-09-14 12:15                 ` Miles Bader
2009-09-14 20:04                   ` tomas
2009-09-12 16:34           ` David Engster
2009-09-13 16:39           ` Richard Stallman
2009-09-13 17:38             ` Eric M. Ludlam
2009-09-14 18:28               ` Richard Stallman
2009-09-13 16:40           ` Richard Stallman
2009-09-07 13:34     ` Richard Stallman
2009-09-08  8:11 ` joakim [this message]
2009-09-08  9:07   ` Lennart Borgman
2009-09-08  9:09     ` Lennart Borgman
2009-09-08 14:41   ` Chong Yidong
2009-09-08 15:10     ` joakim
2009-09-08 17:18       ` Chong Yidong
2009-09-08 21:21     ` Romain Francoise
2009-09-08 22:27       ` Chong Yidong

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3zl95svoq.fsf@verona.se \
    --to=joakim@verona.se \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=tromey@redhat.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.