Hans Aberg <[EMAIL PROTECTED]> writes:
> On 3 Jul 2006, at 22:45, RichAnderson wrote:
>
>> I am attempting to port Bison 2.0 to a machine which uses the EBCDIC
>> character set. This version of bison wants to use itself to rebuild
>> parse-gram.y.
It shouldn't want to do that, unless you've modif
This is probably a question for the Bison Bugs
list; followups, drop Help-Bison cc.
On 3 Jul 2006, at 22:45, RichAnderson wrote:
I am attempting to port Bison 2.0 to a machine which uses the EBCDIC
character set. This version of bison wants to use itself to rebuild
parse-gram.y. This assume
> I want to encapsulate a C++ class ,which can works like a calculator,its
> structure seems like this:
> Class Calc
> {
> //in yylex, result will be evaluated...
>
> };
> In an other word, Can yylex ,yyparse() be encapsulated in a C++ Class ?
Hi,
"Can...". Yes, but you will nee
Hi everyone,
I am a beginner of Flex and Bison and just know litter about them ,I need
your help.
I want to encapsulate a C++ class ,which can works like a calculator,its
structure seems like this:
Class Calc
{
public:
Calc(){};
~Calc(){};
void setExpr(char *cExpr){this->cExpr = cExpr;}
I am attempting to port Bison 2.0 to a machine which uses the EBCDIC
character set. This version of bison wants to use itself to rebuild
parse-gram.y. This assumes that the existing version is the correct code
set. I can't use 1.875 (which I have successfully ported), since it can't
process the p
Please keep the cc to the list, so others get to know the state of
the matter.
On 3 Jul 2006, at 10:48, Wang Yige wrote:
Thank you very much for your "there should be no space after '-o'.
" and I will consult my problem with help-flex .
Thanks again:)
From: Hans Aberg <[EMAIL PROTECTED
[As you did not cc he Help-Bison list, I have to resend. If want to
have more replies and let other know the state of the matter, you
should to send it to the Help-Bison or Flex lists.]
On 3 Jul 2006, at 05:33, Wang Yige wrote:
...when I try "flex -o calc++-scanner.cc calc++-scanner.ll" on m
On 3 Jul 2006, at 10:43, chinlu chinawa wrote:
What I'm looking for is a parser, or as I understand
it, a way in which I can define new keywords whilst
being able to process them as well as any arguments it
may take.
Keywords, or hardwired names, are normally added in the lexer, which
may be
>A LR(1) parser or parser generator? - The latter is
>described in books like the one by Aho, et al.
>"Compilers..." ("The Dragon Book"). You may also
>want to consult the Usenet newsgroup comp.compilers,
>and its FAQ published there monthly. Bison uses
>LALR(1), and its manual gives examples of
