![]() ![]() If you want to get even fancier with features such as live-compiles/on-the-fly syntax checking and code refactoring then I presume the IDE even needs a deeper understanding of the langugage. Slickedit actually supports code completion for mono now for those that are interested. Slickedit for unix does it, but it’s not open source and it’ll set you back a few hundred backs. ![]() ![]() I think Kdevelop has been working on a new parse(I haven’t tried it yet) and the CDT project for Eclipse is working on it, but it’s still no there yet(that I know of). This is the reason you don’t see more support for proper code completion for a complex language like c++. A trivial subset of proper code completion is that you “tag”, index libraries on IDE/editor installation and then you can just look up library types as they’re typed in, but that doesn’t support user defined types/methods. The reason is that if you want to do it right you have to hold a parse tree of your entire projects source code and also do parsing on the fly. Proper “code completion”, “intellisense” is not a trivial matter. This would solve that half of the equation but not auto-completion, but I am not sure there is an easy way to do that anyways. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |