<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-forward-container"><span id="gmail-result_box"
class="gmail-" tabindex="-1" lang="en"><span class="gmail-">The
lambda user who makes use of macros written by a third party
will have a real problem.</span> <span class="gmail-">When a
library crashes because of a missing closing parenthesis while
it still works, and that in addition, the library will be
locked and nobody will remember the password ...</span></span><br>
<span id="gmail-result_box" class="gmail-" tabindex="-1" lang="en"><span
class="gmail-"></span></span>
<div dir="ltr">
<div>
<div><span id="gmail-result_box" class="gmail-" tabindex="-1"
lang="en"><span class="gmail-"><br>
</span></span><span id="gmail-result_box" class="gmail-"
tabindex="-1" lang="en"><span class="gmail-">I think the
only way out will be to orient the user to the "Do not
check Basic syntax strictly" option (I agree with
Jean-Pierre for a less cryptic term).</span> <span
class="gmail-">But the option must remain accessible via
the LO options interface and not via the IDE. </span></span><span
id="gmail-result_box" class="gmail-" tabindex="-1"
lang="en"><span>The implementation of the option will have
to be closely monitored to ensure its deprogramming
(after all, it is a crutch) and it should be reserved
for strict cases of transition to an interpreter</span>
<span>StarBasic cleaner.<br>
<br>
</span></span></div>
<span id="gmail-result_box" class="gmail-" tabindex="-1"
lang="en"><span>Pegards,<br>
<br>
</span></span></div>
<span id="gmail-result_box" class="gmail-" tabindex="-1"
lang="en"><span>Pierre<br>
</span></span></div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2017-06-29 6:12 GMT-04:00 Jean-Pierre
Ledure <span dir="ltr"><<a href="mailto:jp@ledure.be"
target="_blank" moz-do-not-send="true">jp@ledure.be</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">The
default bahaviour of any Basic interpreter should be IMHO to
check the syntax as strictly as possible.<br>
<br>
On the other side tons of legacy Basic sources will not
compile anymore, - including the Basic libraries
(Access2Base, ...) delivered with LO unless they're patched
on time !<br>
<br>
I do support Pierre's proposal to have an option to
(temporarily) *uncheck* the strict syntax checking,<br>
However<br>
- the option should be easily visible and accessible from
the Basic IDE (f.i. not after having checked "enable
experimental features" first ...)<br>
- the text of the option should be less cryptic then
"StarBasic Pragma Strict", but preferably something like "Do
not check Basic syntax strictly"<br>
- Release Notes and help pages should inform the users in
detail<br>
- the option should remain during a long enough period of
time<br>
<br>
JP<br>
<br>
<br>
Le 28/06/17 à 13:08, Kaganski Mike a écrit :<span class="im
HOEnZb"><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 6/28/2017 2:03 PM, Stephan Bergmann wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 06/28/2017 12:12 PM, Pierre Lepage wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
The solution brings a lot of hassle for customers of
the LibreOffice<br>
suite whose work relies on the performance of
StarBasic macros written<br>
by third parties. Macros containing code in error by
the absence of a<br>
closing parenthesis suddenly cease to function. For
this reason, the<br>
patch has not been released. Here I want to explore
a transitional<br>
solution by getting your feedback first. This is to
include in<br>
StarBasic options dialog accessible to the client a
"StarBasic Pragma<br>
Strict" option (checkbox) by which the client
consciously activates<br>
the solution (the patch that has not been
published!). This check box<br>
would be available for a few years with a warning to
prompt<br>
programmers and customers to require their
programmer to correct their<br>
default code on the closing parenthesis.<br>
</blockquote>
Another option might be to have some form of such a
pragma in individual<br>
BASIC source files, instead of as an IDE option. (And
have the pragma<br>
enabled in the "REM ***** BASIC ****** Sub Main ...
End Sub" boilerplate<br>
that is automatically present in a fresh source
file.) That way, users<br>
could enable it for their own, new code, while
(implicitly) keeping it<br>
off for non-conforming old, 3rd-party code.<br>
</blockquote>
I'd suggest also a special handling of "Compile" IDE
command. It should<br>
always use strict parsing method. As it is a developer's
tool, used when<br>
something is created anew, it would help all developers
catch the<br>
problem early even when they don't know the strict
option (wherever it be).<br>
<br>
</blockquote>
<br>
</span>
<div class="HOEnZb">
<div class="h5">
______________________________<wbr>_________________<br>
LibreOffice mailing list<br>
<a href="mailto:LibreOffice@lists.freedesktop.org"
target="_blank" moz-do-not-send="true">LibreOffice@lists.freedesktop.<wbr>org</a><br>
<a
href="https://lists.freedesktop.org/mailman/listinfo/libreoffice"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.freedesktop.org/<wbr>mailman/listinfo/libreoffice</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</body>
</html>