<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Incorrect syntax does compile, MID without end bracket"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=80731#c37">Comment # 37</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Incorrect syntax does compile, MID without end bracket"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=80731">bug 80731</a>
from <span class="vcard"><a class="email" href="mailto:ge.huber@gmx.net" title="ge.huber@gmx.net">ge.huber@gmx.net</a>
</span></b>
<pre>Some time has passed now, since 2014-06-30
and also since Pierre's solution on 2016-11-30.
LO still does it's devil-may-care-cowboy compile
and what may be worse, Pierre's crash scenario
from 2016-10-04 still renders LO unresponsive.
The end of the proposed "limited time period
(3 to 4 years)" draws closer. The option dialog
on my 6.0.7.3 doesn't even have Basic IDE Options.
I'm not aware of "... an application (macro?)
Which would analyze the code to detect all
cases of missing closing parentheses. ".
Calling this proposal D) the de facto winner n
ow seems to be
"C) tolerate the current situation and not change anything?"
So is this ever going to change?
Building on D) I want to propose E)
Don't flag the error, but at least write it
to some basic-compile-warning.log file, which
should be mentioned in the BASIC-help system.
So, what should be done now?
A) code for an exception (Volga)?
B) code for an option on rigor (ge.huber)?
C) tolerate the current situation and not change anything?
D) provide a code analyzer?
E) code a warning log?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>