Bug #6712 2006-03-08 12:14
jgds100
(comments incorrectly colored with line continutation)
Adding items to the TO-DO list through the dialogue allows multiple lines in the item text.
For example, putting the following in the text box (with C++ style comments):
qwertyuiop[newline]
qwertyuiop[newline]
generates in the code file:
// TODO (jgds100#1#): qwertyuiop\
qwertyuiop
note: using C style comments is fine as */ copes with multiple lines.
note2: this error also occurs with TODO items added as compiler warnings or errors.
This problem is only with forced newlines, wrapping text does not have the issue. Perhaps newlines should not be allowed. Especially as the TO-DO list interface (message toolbar) cannot use multiple lines
btw. love Code::Blocks
- Category
- Application::Editor
- Group
- Status
- Closed
- Close date
- 2006-09-08 11:46
- Assigned to
History
I don't understand, what is the bug ??
By the way : I get :
// TODO (jgds100#1#): qwertyuiop\
qwertyuiop\
By the way, which version did you use ?
If you did not try a nighly build, try it out with a recent nightly build please, and provide your feedback in here.
Cheers,
Lieven
I can't confirm rev 2199. It works for me. This is the code.
#include <iostream>
// TODO (Seth#1#): Test\
Test\
Test\
int main(int argc, char* argv[])
{
return 0;
}
sorry for the lack of clarification - been busy. I realise my description was no help.
The bug is with the syntax highlighter. Inserting multiline todo list items compiles fine, but the 2nd and higher lines are syntax highlighted as normal code, not comment.
for example, see
http://homepages.cs.ncl.ac.uk/john.shearer/tmp/CB_todolist_bug.gif
again, this only occurs with todo list items insert as C++ style comments, not with C style comments, or compiler warnings/errors
i hope that clarifies. btw. that with nightly build from March 15 2005
Cheers
John
ok, it's not the fault of the to-do plugin.
It is a more general problem.
type the following code :
// test\
test
the first line is correctly colored, but the second is colored as normal code and not as comments.
So the color coding can't deal with the continuation character '\'
So it is a wxScintilla problem....... :P
I think this is not a bug but a scintilla property setting but I can't remember which one right now...
That is a known Scintilla 1.66 regression, which was supposedly fixed in 1.67. However, I see no difference... :(
I've read the documentation in question and looked at the CPP lexer source.
The only things configurable via properties are folding and styling inside preprocessor directives.
The lexer *does* handle line continuation for preprocessing directives (LexCPP.cxx, lines 80, 111-119, 152-155).
However, it does *not* handle line continuation for comment lines at all (LexCPP.cxx, lines 165-179).
Guess we'll have to wait for the Scintilla guys to implement this.
Umm 1.68 is out maybe it fixes the problem???
This is a scintilla bug. When they fix it, we will too.