whose bug is it ?

[Anonymous_Banned275]

Just a comment (rant ) , I do not expect a solution.

When the long single line of code "extends" to another editor line
and gets commented out ("//") the compiler skips only the first line

// connect(ui->list, SIGNAL(itemActivated(QListWidgetItem*)),
this, SLOT(itemActivated(QListWidgetItem*)));

Just a comment (rant ) , I do not expect a solution.

[Christian Ehrlicher]

I would guess you should ask the C standards committee to 'fix' it...

[Kent-Dorfman]

It's the editor text wrapping setting.

The C/C++ // standard only applies to text lines that don't contain any \n or \r chars. if you look at the source file using od -cx you'll see that the text wrap is inserting newline chars.

you can/should use /* */ format to avoid this.

[JoeCFD]

@AnneRanch said in whose bug is it ?:

// connect(ui->list, SIGNAL(itemActivated(QListWidgetItem*)),
this, SLOT(itemActivated(QListWidgetItem*)));

// connect(ui->list, SIGNAL(itemActivated(QListWidgetItem*)),
//this, SLOT(itemActivated(QListWidgetItem*)));

or
/* connect(ui->list, SIGNAL(itemActivated(QListWidgetItem*)),
this, SLOT(itemActivated(QListWidgetItem*))); */

or 
#if 0
connect(ui->list, SIGNAL(itemActivated(QListWidgetItem*)),
this, SLOT(itemActivated(QListWidgetItem*))); 
#endif

[Anonymous_Banned275]

@JoeCFD Sorry , I did not ask for alternative solution, and there are no escape characters in the affected line either.
My uneducated guess is - when the "//" definition is to skip until new line
it should do so .
The compiler is working fine detecting the "new line " created by the editor.
Reader if free to interpret my uneducated guises to his liking.
END OF RANT