The new Release 20.03 is out! You can download binaries for Windows and many major Linux distros here .
CCFileType CCFileTypeOf(const wxString& filename){ const wxString file = filename.AfterLast(wxFILE_SEP_PATH).Lower(); const int pos = file.Find(_T('.'), true); wxString ext; if (pos != wxNOT_FOUND) ext = file.SubString(pos + 1, file.Len()); if ( ext.IsEmpty() || ext == _T("h") || ext == _T("hpp") || ext == _T("tcc") || ext == _T("xpm") ) { return ccftHeader; } else if ( ext == _T("cpp") || ext == _T("c") || ext == _T("cxx") || ext == _T("cc") || ext == _T("c++") ) { return ccftSource; } else return ccftOther;}
The best way is that it can have a wxTextCtrl in the CC setting dialog.
But this I think is belong to "code completion" page, not the parser page.
PS: I'm not sure our CC's parser can correctly parse java source files.
Implemented in trunk.
I've set the category to Lexer, is this the correct one?
Probably only developers can change the 'advanced' settings of patches, bugs and features.
is there any structure in place that I can use to create "on demand" code completion (similar to being able to select the lexer with Edit->Highlight mode)?
Quote from: ollydbg on January 03, 2012, 08:42:21 amBut this I think is belong to "code completion" page, not the parser page.True, I actually had in mind to save space... I'll change it.
As we can't not multiply select many items, so even cut/paste every items in "Keyword sets to additionally include" are quite annoying.