Re: Looking for a fast C++ parser

"Peter \"Firefly\" Lund" <firefly@diku.dk>
16 Aug 2005 11:14:51 -0400

          From comp.compilers

Related articles
[2 earlier articles]
Re: Looking for a fast C++ parser snicol@apk.net (Scott Nicol) (2005-08-10)
Re: Looking for a fast C++ parser vidar.hokstad@gmail.com (Vidar Hokstad) (2005-08-10)
Re: Looking for a fast C++ parser firefly@diku.dk (Peter \Firefly\Lund) (2005-08-13)
Re: Looking for a fast C++ parser snicol@apk.net (Scott Nicol) (2005-08-16)
Re: Looking for a fast C++ parser Martin.Ward@durham.ac.uk (Martin Ward) (2005-08-16)
Re: Looking for a fast C++ parser firefly@diku.dk (Peter \Firefly\Lund) (2005-08-16)
Re: Looking for a fast C++ parser firefly@diku.dk (Peter \Firefly\Lund) (2005-08-16)
Re: Looking for a fast C++ parser snicol@apk.net (Scott Nicol) (2005-08-16)
Re: Looking for a fast C++ parser firefly@diku.dk (Peter \Firefly\Lund) (2005-08-16)
| List of all articles for this month |

From: "Peter \"Firefly\" Lund" <firefly@diku.dk>
Newsgroups: comp.compilers
Date: 16 Aug 2005 11:14:51 -0400
Organization: Compilers Central
References: 05-06-133 05-08-030 05-08-035 05-08-051 <42FD7FC1.4040704@apk.net>
Keywords: C++, parse, tools

On Sat, 13 Aug 2005, Scott Nicol wrote:


> As with every design, there are trade-offs. The current fashion adds a lot
> of flexibility to support multiple languages, and the ability to add support
> new languages without modifying the editor.


Of the editors I have used, Aurora was the one it was easiest to add
new language highlighting for.


It used the approach I am advocating.


> On the flip side it wastes a few MHz of your x.y GHz CPU and a
> couple hundred K out of your GB of RAM.


Not just a few MHz, I am afraid. It makes loading of new files a lot
slower and screen update sluggish. I also want the screen to react in
100ms or less when I type (I have very fast reflexes) otherwise it
feels "wrong". Deleting or inserting '/*' should not result in
noticeable delays (vim) or miscolouring (Emacs).


-Peter


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.