Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.compilers > #722
| From | hsad005@gmail.com |
|---|---|
| Newsgroups | comp.compilers |
| Subject | Bison deterministic LALR(1) parser for Java/C++ (kind of complex langauge) without 'lexar hack' support |
| Date | 2012-08-17 11:22 -0700 |
| Organization | Compilers Central |
| Message-ID | <12-08-005@comp.compilers> (permalink) |
I need to write a parser for a programming langauge which is as complex as C++/Java, and to even complicate the matter, there are constructs in this langauge that doesn't allow me to use type/identifier dis-ambiguating lexer hack. In other words, I will have to return just one lexical token (say IDENTIFIER) from the lexer for both type references as well as non-type variable references. Given these restrictions, I was wondering if it would be a good idea to pick yacc/bison for my parser...? Or, should I consider a hand written recursive descent parser. Regards. [Get it working in bison, then in the unlikely event that's not fast enough, profile your compiler to see where it's spending its time and fix what needs to be fixed. Although in theory GLR can be very slow, in practice the ambiguities are generally resolved within a few tokens and the performance is fine. compilers always spend way more time in the lexer than the parser anyway. Writing RD parsers by hand can be fun, but you never know what language it actually parses. -John]
Back to comp.compilers | Previous | Next — Next in thread | Find similar
Bison deterministic LALR(1) parser for Java/C++ (kind of complex langauge) without 'lexar hack' support hsad005@gmail.com - 2012-08-17 11:22 -0700
Re: Bison deterministic LALR(1) parser for Java/C++ (kind of complex langauge) without 'lexar hack' support Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2012-08-18 10:13 +0100
Re: lexer speed, was Bison Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2012-08-20 01:01 +0100
Re: lexer speed, was Bison Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2012-08-20 16:14 +0100
Re: lexer speed, was Bison BGB <cr88192@hotmail.com> - 2012-08-20 14:14 -0500
Re: lexer speed, was Bison Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2012-08-21 07:40 +0100
Re: lexer speed, was Bison "BartC" <bc@freeuk.com> - 2012-08-21 17:39 +0100
Re: Bison deterministic LALR(1) parser for Java/C++ (kind of complex langauge) without 'lexar hack' support anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2012-08-20 13:35 +0000
Re: Bison deterministic LALR(1) parser for Java/C++ (kind of complex langauge) without 'lexar hack' support BGB <cr88192@hotmail.com> - 2012-08-21 14:45 -0500
Re: Bison deterministic LALR(1) parser for Java/C++ (kind of complex langauge) without 'lexar hack' support "BartC" <bc@freeuk.com> - 2012-08-22 14:04 +0100
Re: Bison deterministic LALR(1) parser for Java/C++ (kind of complex langauge) without 'lexar hack' support BGB <cr88192@hotmail.com> - 2012-08-26 19:37 -0500
Bison deterministic LALR parser for Java/C++ "BartC" <bc@freeuk.com> - 2012-08-29 22:03 +0100
speeding up C recompilation, was Re: Bison deterministic LALR BGB <cr88192@hotmail.com> - 2012-09-04 13:45 -0500
Re: C include handling, was Bison deterministic LALR Marco van de Voort <marcov@toad.stack.nl> - 2012-09-05 08:40 +0000
Re: Bison deterministic LALR(1) parser for Java/C++ (kind of complex langauge) without 'lexar hack' support hsad005@gmail.com - 2012-08-18 02:09 -0700
csiph-web