> I mean what about project own headers ? Will they be parsed or no?
of cource. Anjuta has it's own library called tag manager, which manages those. It's built on top of ctags.
> Do You have any library (dll) for this (using external ctags would be horrible)
no
> Could You tell what is wrong with current parser and what are the benefits of using Scintilla, and what will change.
there's a lot of things wrong with the current parser - just browse through bugs and RFEs. Scintilla is in constant development, and cppparser is really not - only devcpp uses it. same with synedit - there are not many projects that really use it (I think mainly beacuse it's for delphi and written in pascal). Just by switching to scintilla it would solve most of the devcpp cppparser bugs and RFEs. And we wouldn't have to reinvent the wheel - someone else has already done it why not use it?
I don't see any negatives in the change. Dev-cpp would have to come with scilexer.dll - I don't know if it's a problem for anyone
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well,yes - TCppparser is buggy in his work.You are right, switching to scintilla could be step forward.I doubt if it have better performance anyway (ctags is not formal database just linked list of files as I know - correct me if I'm wrong)
If we stict to C++ in generating class tree,tooltips and autocompletion feature then we could consider generating parser by using Bison, Yacc or Lemon (i'm not keen on those parser generators nor using them anyway , but there are ready grammar syntax for most of them)
Regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've just upgraded the dev-cpp cvs to synedit current (2.0 beta?). I hope it's going to fix some problems reported. If anyone experiences problems with this build, please let me know. The location of that build is here: http://www.castlesofpoland.com/dev-cpp/devcpp.exe
As always there may be some problems with icons/associations. I'm going to fix it sometime soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> Please explain in detail how parser,code completion ,tooltips will work under Scintilla ?
the best way to see it working is to try anjuta. but there's a lot of other projects using it to try how all those features work: http://scintilla.sourceforge.net/ScintillaRelated.html
> I mean what about project own headers ? Will they be parsed or no?
of cource. Anjuta has it's own library called tag manager, which manages those. It's built on top of ctags.
> Do You have any library (dll) for this (using external ctags would be horrible)
no
> Could You tell what is wrong with current parser and what are the benefits of using Scintilla, and what will change.
there's a lot of things wrong with the current parser - just browse through bugs and RFEs. Scintilla is in constant development, and cppparser is really not - only devcpp uses it. same with synedit - there are not many projects that really use it (I think mainly beacuse it's for delphi and written in pascal). Just by switching to scintilla it would solve most of the devcpp cppparser bugs and RFEs. And we wouldn't have to reinvent the wheel - someone else has already done it why not use it?
I don't see any negatives in the change. Dev-cpp would have to come with scilexer.dll - I don't know if it's a problem for anyone
Well,yes - TCppparser is buggy in his work.You are right, switching to scintilla could be step forward.I doubt if it have better performance anyway (ctags is not formal database just linked list of files as I know - correct me if I'm wrong)
If we stict to C++ in generating class tree,tooltips and autocompletion feature then we could consider generating parser by using Bison, Yacc or Lemon (i'm not keen on those parser generators nor using them anyway , but there are ready grammar syntax for most of them)
Regards
I've just upgraded the dev-cpp cvs to synedit current (2.0 beta?). I hope it's going to fix some problems reported. If anyone experiences problems with this build, please let me know. The location of that build is here: http://www.castlesofpoland.com/dev-cpp/devcpp.exe
As always there may be some problems with icons/associations. I'm going to fix it sometime soon.
Here's the Lazarus roadmap.
http://www.lazarus.freepascal.org/modules.php?op=modload&name=Roadmap&file=index
You'd need to checkout if dev-cpp uses ANY components that are in yellow (in-progress) or red (not-implemented).
The "not-implemented" mean that NOBODY is working on it, so they NEED volunteers.
So far:
-------
GTK2 General interface in progress
Win32 General interface in progress
GTK Doublebuffering in progress
GTK Graphics in progress
-------
Components:
TCheckListBox in progress
CUPS package
and example not implemented
TIcon not implemented
TPrinterSetupDialog not implemented
-------------
LCL:
Everything but "Port to Darwin Power PC, Mac OS X","TAction","TSplitter" are either in-progress or not implemented.