From: Richard Stallman <rms@gnu.org>
To: eric@siege-engine.com
Cc: cyd@stupidchicken.com, raeburn@raeburn.org, deng@randomsample.de,
emacs-devel@gnu.org
Subject: Re: CEDET merge question
Date: Sun, 13 Sep 2009 12:40:45 -0400 [thread overview]
Message-ID: <E1Mms85-0007kJ-Mb@fencepost.gnu.org> (raw)
In-Reply-To: <1252759780.4770.76.camel@projectile.siege-engine.com> (eric@siege-engine.com)
I don't know how bison works, but I would assume that bison parses basic
C code (thus replacing $1 with some other piece of code.) In the same
way, it would need to be taught about Emacs Lisp, Scheme, or any other
language someone might want.
Bison parses grammar definition files, which can contain segments of code.
Normally the syntax for a segment of code is {...}.
Bison generates tables for a parser, and puts the segments of code
into a function to do the parsing. Normally that function is written
in C.
However, using a different language and different syntax is just a
superficial change.
The end result, however, would involve rather extreme
changes to bison, and possibly flex if flex is also used.
Oh no. The complex parts of Bison would not be changed at all.
Only some of the parser and the output code. These are the parts that
are easy to understand, without even minimal knowledge of parsing.
next prev parent reply other threads:[~2009-09-13 16:40 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 [this message]
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=E1Mms85-0007kJ-Mb@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=deng@randomsample.de \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
--cc=raeburn@raeburn.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).