From: David Engster <deng@randomsample.de>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: CEDET merge question
Date: Sat, 05 Sep 2009 19:22:46 +0200 [thread overview]
Message-ID: <87iqfx5ms9.fsf@engster.org> (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:
> 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 think it depends on the question if people should be able to edit and
compile the grammars itself, only using Emacs proper.
The bovine/wisent parsers and major-modes are crucial for development,
but I think they are not necessarily needed for the resulting parser; I
may be wrong though, especially when it comes to the Wisent parser,
which I'm not familiar with at all.
For example, the file semantic/bovine/c.by is the Bison grammar for
C/C++ parsing. During CEDET's make process, the 'bovine' code generates
the file semantic/bovine/semantic-c-by.el, which is the resulting C(++)
lexer in Emacs Lisp. This file is then required by
semantic-c.el. Therefore, I would think that including the resulting
semantic-c-by.el should be enough for the C parser to be working.
As mentioned above, there are also the major-modes for bison/wisent in
CEDET (bovine-grammar.el, wisent-grammar.el) which are needed for
writing and debugging the grammar files. I think those would also not
necessarily be needed in Emacs. However, if people would like to extend
or fix grammar files (or write new ones), they would then have to get
CEDET from CVS.
> (Wisent, for instance, appears to be an entire Elisp reimplementation
> of Bison...)
Yes, it is exactly that. :-)
Regards,
David
next prev parent reply other threads:[~2009-09-05 17:22 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 [this message]
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
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=87iqfx5ms9.fsf@engster.org \
--to=deng@randomsample.de \
--cc=cyd@stupidchicken.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 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.