To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=59790





------- Additional comments from [EMAIL PROTECTED] Wed Jan 18 05:59:33 -0800 
2006 -------
> - this should be properly documented in the on-line help (and in StarOffice 8 
> Programmer's Guide)

But it is documented. In the current (m150) online help I found under
"The Basic Editor" - ok, maybe this is not the most adaquate place:

    Long lines can be split into several parts by inserting an 
    underline character _ as the last character of a line. This 
    connects the line with the following line to one logical line.

 - the syntax coloring in the IDE should "know" this new feature : today it 
still 
colors reserved words in the subsequent comment line.

Right, this indeed is a bug. But as it is surpisingly difficult to
fix and I don't consider the whole "REM _" scenario as particularly
important, I doubt that it has a chance to be fixed very soon. There
are simply too many more important tasks.


> About the consequences of the current design, a macro with an ending _ in a
comment may 
> work incorrectly, or not at all, because the next line will not be executed. 
> You 
> cannot say "there is no crash, no data loss", anything can happen, with any 
> consequence.

The only problem I see is that the behaviour changed. But the old be-
haviour just was wrong taking VB as reference. This problem will be
solved with my fix. It's correct, that the next line will not be exe-
cuted with the new behaviour, but this should be no problem as nobody
needs to use " _" at the end of a comment line and if he does, al-
though the next line should be executed, it's just a bug in the macro.

Still I think this problem really shouldn't be overrated. I deal with
OOo Basic / Star Basic for nearly ten years now and before fixing the
internal issue 124674 for 2.0.1, I've never seen one single macro with
a comment ending on " _". And that's no surprise for me, as the benefit
seems to be extremely limited. It's much clearer to also comment the 
next line instead of extending the comment from the previous line.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to