<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - Macro Creates Formulas with Error 508"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=101316#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - Macro Creates Formulas with Error 508"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=101316">bug 101316</a>
from <span class="vcard"><a class="email" href="mailto:ghborrmann@gmail.com" title="ghborrmann <ghborrmann@gmail.com>"> <span class="fn">ghborrmann</span></a>
</span></b>
<pre>(In reply to Mike Kaganski from <a href="show_bug.cgi?id=101316#c7">comment #7</a>)
<span class="quote">> oCell.Formula takes *standard* (language-independent) syntax of formulas
> (using ';' for function argument separators, among other things), so
> "=IF(A2="",B1,B2)" is of course an invalid input resulting in error from
> parsing the formula text. This is not a bug.</span >
Where does is state that using ';' for function argument separators is
standard? LO itself acknowledges that the comma is standard, in two ways:
1. When entering a formula from the keyboard, LO shows a template of the
function. This template uses commas, not semicolons.
2. When a formula is created by a macro, using semicolons results in no error
but clicking on the cell shows that the formula now in the cell uses commas.
My point: this bug, while trivial for experienced LO macro writers, can give
new users a bad impression of LO's overall quality.</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>