unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: David Engster <deng@randomsample.de>
Cc: emacs-devel@gnu.org
Subject: Re: CEDET merge question
Date: Sat, 05 Sep 2009 16:53:40 -0400	[thread overview]
Message-ID: <87iqfxru3v.fsf@cyd.mit.edu> (raw)
In-Reply-To: <87iqfx5ms9.fsf@engster.org> (David Engster's message of "Sat, 05 Sep 2009 19:22:46 +0200")

David Engster <deng@randomsample.de> writes:

> 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.

I see.  I think it's better for us to merge just the generated Lisp
grammar files, leaving the grammar development for upstream.  It's an
awful lot of infrastructure to pull in, considering that CEDET
development won't be carried out in our repository anyway.

Do you know if the bovine and wisent parsers are mutually replacable?
For instance, the default parser seems to be bovine; would it be a big
deal if we included just the bovine parser?




  reply	other threads:[~2009-09-05 20:53 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 [this message]
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

  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=87iqfxru3v.fsf@cyd.mit.edu \
    --to=cyd@stupidchicken.com \
    --cc=deng@randomsample.de \
    --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).