|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
|
Last edited by ReedN on Tue Sep 21, 2010 5:56 am; edited 2 times in total |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Sat Sep 18, 2010 5:37 pm |
That is correct. The // at the beginning of the line is actually treated as a ; comment by the parser, and 3.27 fixed the bug that was indenting comments. So comments will now get left alone by the reformat.
|
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Sat Sep 18, 2010 5:43 pm |
The '//' comments looked better how it was previously. Now the comments don't match up with the text that it goes with. It makes it ugly and a lot harder to scan visually.
|
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Sat Sep 18, 2010 5:48 pm |
I'll see what I can do. If it's an easy parser fix then I'll do it, but I don't want to cause some side effect in the parser that screws up comments. As I said, it's an issue in that the parser returns the same tokens for // at the beginning of a line and ; and the ; comment cannot be indented by the reformat without messing up the script. So it's not the reformatter that I'd have to change, it's the parser itself. I'm nervous about changing anything in the parser this close to a release.
But if it's easy, I'll try it. |
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Tue Sep 21, 2010 5:54 am |
Confirmed fixed in 3.28.
|
|
|
|
|
|