<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi,</p>
<p><span id="result_box" class="" tabindex="-1" lang="en"><span>Indeed,
I also do not see the reason for having to check "</span></span><span
id="result_box" class="" tabindex="-1" lang="en"><span><span
id="result_box" class="short_text" tabindex="-1" lang="en"><span>Enable
experimental functions (may be unstable)</span></span>".</span>
<span>Can we remove this step and thus make the StarBasic IDE
available by default without more fuss? </span></span><br>
<span id="result_box" class="" tabindex="-1" lang="en"><span>Also,
a kind of "strict" compilation mode on demand seems to me
difficult to defend.</span> <span>How do we notify customers
about this inconsistency of the StarBasic interpreter? </span></span><br>
<span id="result_box" class="" tabindex="-1" lang="en"><span>I
have a suggestion.</span> <span>We include by default (but
only for a time limit of some revisions) an error tolerance of
the closing parenthesis.</span> <span>And let's set a warning
to compile (as in gcc).</span> <span>Here, it would be
necessary for the compiler to have the ability to output a
list of all the places in the code where a closing parenthesis
is missing.</span> <span>Otherwise, the compiler that stops
with each error is really annoying and is wasting time on the
programmer who wants to fix the problem.</span></span></p>
<p><span id="result_box" class="" tabindex="-1" lang="en"></span><span
id="result_box" class="" tabindex="-1" lang="en"><span>The
warning message could read as follows:</span><br>
<br>
<span>Warning: One or more closing parentheses are missing in
one or more expressions.</span></span></p>
<p><span id="result_box" class="" tabindex="-1" lang="en"><span>Regards,</span></span></p>
<p><span id="result_box" class="" tabindex="-1" lang="en"><span>Pierre<br>
</span></span></p>
<br>
<div class="moz-cite-prefix">Le 2017-07-06 à 04:08, Katarina Behrens
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:1556152.kyyqVaEp1E@localhost.localdomain">
<pre wrap="">Hello world,
I kinda like Mike's proposal to use strict checking when test-compiling the
code in IDE
</pre>
<blockquote type="cite">
<pre wrap="">I do support Pierre's proposal to have an option to (temporarily)
*uncheck* the strict syntax checking,
However
- the option should be easily visible and accessible from the Basic IDE
(f.i. not after having checked "enable experimental features" first ...)
</pre>
</blockquote>
<pre wrap="">
I do get the reasoning why Basic IDE branch of Tools > Options tree was made
invisible (because the checkboxes therein were inactive without enabling
experimental mode) ...
... but I somehow fail to see what is so experimental about those IDE options
(unless of course ~all of development in Basic is considered to be an
experiment :grin: )
</pre>
</blockquote>
<br>
</body>
</html>