unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
To: David Engster <deng@randomsample.de>
Cc: Chong Yidong <cyd@stupidchicken.com>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: CEDET merge question
Date: Sun, 6 Sep 2009 18:26:33 -0400	[thread overview]
Message-ID: <AD466322-19DE-4B69-B9F7-72BE090D114B@raeburn.org> (raw)
In-Reply-To: <87k50bixsl.fsf@engster.org>

On Sep 6, 2009, at 17:11, David Engster wrote:
> Ken Raeburn <raeburn@raeburn.org> writes:
>> On Sep 6, 2009, at 11:37, Richard Stallman wrote:
>>> Is it possible to use Bison itself rather than implement the
>>> same functionality differently?  Or perhaps add an option
>>> to Bison to output its data in whatever format is convenient?
>>
>> Guile is also using a translation/reimplementation of Bison in  
>> Scheme.
>> I haven't looked at the CEDET code, but Guile's version wants  the
>> grammar input using Scheme (s-expression) syntax.
>
> CEDET uses Bison grammars which are extended through "Optional Lambda
> Expressions" (OLE). They produce the actual tags, which are the basic
> objects resulting from the parsing stage. I don't think this can be
> easily replaced by Bison itself or Guile.

Sorry, I didn't mean to suggest replacing it with Guile, more that, if  
the requirements were similar enough, Bison extensions to support both  
CEDET and Guile might be possible.  But if you're extending the  
grammar with Lisp code, that may not be feasible....

Ken




  reply	other threads:[~2009-09-06 22:26 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 [this message]
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=AD466322-19DE-4B69-B9F7-72BE090D114B@raeburn.org \
    --to=raeburn@raeburn.org \
    --cc=cyd@stupidchicken.com \
    --cc=deng@randomsample.de \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).