A systematic approach to code completion and c++ parsing/storage

[Thomas Schilling]

> >In a first approach I's suggest leaving out increamental parsing and only
> >parse whole files. But wait: heavn't we already been there. Didn't
> >somebody start with a tokenizer (flex)?
> >
> I did you can get it with:
> export CVSROOT=:pserver:guest at lma.ee.fhm.edu:/home/cvs
> cvs login
> [no password}
> cvs co kdev2_parser

Uhm, seems we have multiple tokenizers. I extended 'tokenizer-cc.l/h'
(C++ Lexer/Tokenizer) a bit (e.g. all keywords)

If someone wants it i can post it as an attachment - but caution: it's
incompatible (e.g: before: "~MyClass" was an ID, now it's '~' + ID)