Developer forums (C::B DEVELOPMENT STRICTLY!) > Contributions to C::B
Using CTags as main parser
eranif:
SQLite can be in-memory too (just set the name of the db in your code to be ':memory:') , however SQLite has some other advantages when used on disk, let say for code completion:
A user wrote 'My' and then pressed a ctrl+space (shorcut for autocompletion) - In my case the solution is easy: select from class_table where name like '%My%'; and thats it! (of course I do the same select on the other tables such as function_table, member_table, prototype_table, concatenates the results and then open the autocompletion box).
Btw, sadly wxScintilla did not implement AutoComplete box yet. (from the screenshots I saw that you guys created one of your own though)
In addition - when u use disk image - when loading the project again - you dont need to parse the files again, they are already parsed!.
More, You can parse third party libraries headers without even including them into your project - just parse them, create a database and the n use it (this approach can also be used to parse the gcc include files and thus creating codecompletion for the C++ language itself and also distibute them with C::B package)
Speed is not an issue, I tested the parser for large projects the speed of selecting from SQLite is very fast (you will not notice that it is on disk)
@Michael:
I just read your other article on Mini C++ parser. You are also mentionaning the Navigation drop down lists, using the same method of SQLite, I achieved that as well (using SCN_UPDATEUI event, I update the drop down lists according to the SQLite db, since the line numbers and file names are kept in the db, the get the relevant info I simply do the following select call:
select scope, name from function_table where line >= <current line number goes here> ORDER BY LINE - this will result with the requested info.
Here is a screenshot of my CLOSED editor (THIS IS NOT A COMMERCIAL, THE PROJECT IS CLOSED) - and see what I achieve with SQLite as DB:
Eran
takeshimiya:
Looks great! :D
I actually think the best solution is to have in C::B, 3 completely different parsers (for some time).
-The current hand-made C++ parser.
-The CTags parser (for all languages supported).
-The ANTLR parser (for all languages supported).
I've talked with the CodeStore author (which uses ANTLR), and it's almost everything we need for C++.
So, actually I would like to see which one is easier to implement (and handles better C++).
mandrav:
--- Quote from: eranif on January 09, 2006, 12:05:49 am ---Btw, sadly wxScintilla did not implement AutoComplete box yet. (from the screenshots I saw that you guys created one of your own though)
--- End quote ---
The AutoCompleteBox is implemented. I didn't use it for other reasons.
Btw, could you send me a mail with the code to look around and run some tests? :lol:
Michael:
--- Quote from: Takeshi Miya on January 09, 2006, 03:19:54 am ---I actually think the best solution is to have in C::B, 3 completely different parsers (for some time).
-The current hand-made C++ parser.
-The CTags parser (for all languages supported).
-The ANTLR parser (for all languages supported).
--- End quote ---
I think that your suggested solution is good :D. I do not know exactly the roadmap for C::B, but IMHO it would be worth before the release of C::B 1.0 to implement and test the current hand-made C++ parser, CTags parser and ANTLR parser. In this way it would be possible to decide which parser (or parsers :)) best fit C::B needs.
@rickg22: If I remember your parser is table-driven based, right? IMO your rewrite is worth of consideration and implementation :D.
@eranif: Thank you very much for all the explanations. XStudio looks really good :).
Michael
rickg22:
--- Quote from: Michael on January 09, 2006, 12:07:16 pm ---@rickg22: If I remember your parser is table-driven based, right? IMO your rewrite is worth of consideration and implementation :D.
--- End quote ---
That's when I get to *START* the rewrite. My current changes (let's call them "phase 1") are optimization ones - got rid of that stupid 3 second delay when reparsing files, minimized the "updating class browser" delay down to 0.5 seconds (on my machine), and the one i'm currently working on is the parser's FindMatches. Unfortunately, in this one, my program segfaults, it seems that the tree structure is corrupted :( I may need 3 or 4 days to catch the bug :(
Then goes phase 2: Getting rid of the "updating class browser" delay at all, and finally i'll start with the rewrite. Won't take long, I hope. It's just matter of converting the parserthread functions to states, and voila :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version