https://bugs.documentfoundation.org/show_bug.cgi?id=173117

            Bug ID: 173117
           Summary: [ScriptForge HELP] Sample formulas for AppendColumn
                    and AppendRow functions do not match their
                    explanations
           Product: LibreOffice
           Version: 27.2.0.0 alpha0+ master
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Documentation
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]

Description:
Sample formulas for AppendColumn and AppendRow functions do not match their
explanations.

Steps to Reproduce:
See ScriptForge.Array service Page

Actual Results:
* AppendColumn:
https://help.libreoffice.org/master/ja/text/sbasic/shared/03/sf_array.html#AppendColumn

c = SF_Array.AppendColumn(Array(), Array(1, 2, 3))
    ' ∀ i ∈ {0 ≤ i ≤ 2} : b(0, i) ≡ i

* AppendRow:
https://help.libreoffice.org/master/ja/text/sbasic/shared/03/sf_array.html#AppendRow

b = SF_Array..AppendRow(Array(), Array(1, 2, 3))
    ' ∀ i ∈ {0 ≤ i ≤ 2} : b(i, 0) ≡ i

Expected Results:
## AppendColumn Function:

c = SF_Array.AppendColumn(Array(), Array(1, 2, 3))
returns
  b(0,0)=1
  b(1,0)=2
  b(2,0)=3
or
  ((1,), (2,), (3,))

---
∀ i ∈ {0 ≤ i ≤ 2} : b(0, i) ≡ i
means
  b(0,0)=0
  b(0,1)=1
  b(0,2)=2
or
  ((0, 1, 2),)

## AppendRow Function:

b = SF_Array..AppendRow(Array(), Array(1, 2, 3))
            ^^
    SF_Array.AppendRow is correct

returns
  b(0,0)=1
  b(0,1)=2
  b(0,2)=3
or
  ((1, 2, 3),)

---
∀ i ∈ {0 ≤ i ≤ 2} : b(i, 0) ≡ i
means
  b(0,0)=0
  b(1,0)=1
  b(2,0)=2
or
  ((0,), (1,), (2,))


Reproducible: Always


User Profile Reset: No

Additional Info:
And,
The notation "∀ i ∈ {0 ≤ i ≤ 2} : b(i, 0) ≡ i" doesn't appear to be standard.

The AI responded as follows:

∀i ∈ {0, 1, 2} : b(i, 0) = i
or
∀i (0 ≤ i ≤ 2 ⇒ b(i, 0) = i)
or
∀i ∈ Z(0 ≤ i ≤ 2 ⇒ b(i, 0) = i)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to