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

[W. Tasin]

Thomas Schilling wrote:

>>>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)
>
My approach was going away from lex- or flex-usage [or yacc/bison-usage] :-)
it interprets a textfile like the lexem-file to have a more generic lexer.

>
>_______________________________________________
>Kdevelop-devel mailing list
>Kdevelop-devel at barney.cs.uni-potsdam.de
>http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-- 
The KDevelop project: tasin at kdevelop.de [www.kdevelop.org]
--
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
(Zucchero)
:-------W. Tasin, FB 04,FHM-------------------PGP-KeyID:0x7961A645----------:
<Key-Fingerprint: 1610 835F 0080 32F4 6140  6CF7 A7D0 44CD 7961A645>