Developer forums (C::B DEVELOPMENT STRICTLY!) > Contributions to C::B
Using CTags as main parser
Game_Ender:
Any word on the integration of eranif's CodeCompletion implementation? It looks very exciting, I too had looked a CTags long ago when the discussion first began. Only eranif did the hard part and actually implemented something with it. It is also important to note the benifit of having an on disk SQLite database is the fact that there is no "Saving or Loading Cache", in fact there would be no cache at all. I also believe that SQLite supports Atomic commits so crashing of the application will not corrupt the database, at least in theory.
eranif:
Hi,
Sorry I didnt have time to work on it yet. later today I will start decoupling the parser code from my old project to make it a standalone component, should not take long maybe a day or two.
Eran
takeshimiya:
--- Quote from: eranif on January 17, 2006, 02:29:26 pm ---Hi,
Sorry I didnt have time to work on it yet. later today I will start decoupling the parser code from my old project to make it a standalone component, should not take long maybe a day or two.
Eran
--- End quote ---
:D
eranif:
Hi,
I started working on decoupling the code parser from my old project, well it seems like alot of work :( ..
So, What I have come out so far is:
I created a small app that does the following:
- Create an empty db with all indexes defined
- Parse sample input files (in batch mode) and populate the db
In the main frame there is a function that called: InitDb()
this is the function the one that should intrest you (all the other files, can be ignored for the moment they are used internally or I will use them later when I will update the demo)
In this file what I do is:
- Open the sample input files and loads their data
- Create language parser (e.g. CPP) - this can easily be extended to other languages as well
- Create the ctags interface
- Execute
- Store the results into SQLite
The db class is called
- USDb
The DB is consistent with 4 tables:
- member_table
- function_table
- class_table
- prototype_table (this is special case of prototype function)
to prevent duplicates, there are indexes on the tables - so duplicate entries are not allowed (but of course, same name different prototype is allowed ...)
This example shows how you can use ctags to create a db with all workspace information saved.
Things it can do but I did not had time to present how to do them (but i will):
- It does not show how to get localmember type (qualifier).
- It does not show how to get the current function class name from cursor location (like the two combo boxes in VC71 located on top of the file)
- It does not suggest members/functions list
- It does not show how to parse local scope (ctags cant parse local variables, this is where my internal parser come to help - lex.yy.cpp & USCPPScanner )
Hopefully tomorrow or during the weekend (the weekend starts here tomorrow :)) I will update the sample with more functionality so you will get the impression of the idea.
To run the sample, place the exe "ctags.exe" udner a valid path - it can be found under "SQLite_db/bin/ctags.exe"
In addition, in order to view the results, I am also providing SQLite browser which I found on SF. it is called "SQLite Database Browser" and can be found under "SQLite_db/bin/" or you can use the simple command line "sqlite.exe"
The database name is "./internals/ctags.db" simply open it with the browser and have a look at the results of the parsing.
The parsing input files (it is actually the Tinyxml code) can be found under "Samples/"
The project can be found here:
http://www.eistware.com/wx/ctags/ctags.zip
Let me know if you had problems or questions,
Eran
Game_Ender:
Awsome keep up the good work. There is nothing holding back linux integration is there, I assume you just chose to do a windows example for easy of use.
On another note SQLite databases allow access by multiple processes that can read from the database at once, and locks the entire database during writing. This would make it pretty easy to thread this sort of CodeCompletion. You would only need to have a thread safe queue of files for the parser worker thread. The worker thread just sits parsing all the files in the queue, hopefully doing batch writes and not a bunch of small ones to the database. Then the main thread can query the database whenever it needs needed without fear of any errors occurring.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version