[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CEDET merge question
From: |
Richard Stallman |
Subject: |
Re: CEDET merge question |
Date: |
Sun, 13 Sep 2009 12:40:45 -0400 |
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.
- Re: CEDET merge question, (continued)
- Re: CEDET merge question, Eric M. Ludlam, 2009/09/12
- Re: CEDET merge question, Miles Bader, 2009/09/12
- Re: CEDET merge question, Richard Stallman, 2009/09/13
- Re: CEDET merge question, tomas, 2009/09/14
- Re: CEDET merge question, Miles Bader, 2009/09/14
- Re: CEDET merge question, tomas, 2009/09/14
- Re: CEDET merge question, David Engster, 2009/09/12
- Re: CEDET merge question, Richard Stallman, 2009/09/13
- Re: CEDET merge question, Eric M. Ludlam, 2009/09/13
- Re: CEDET merge question, Richard Stallman, 2009/09/14
- Re: CEDET merge question,
Richard Stallman <=
- Re: CEDET merge question, Richard Stallman, 2009/09/07
Re: CEDET merge question, joakim, 2009/09/08