ISEVEN_ADD Function (OpenOffice Calc)

• Introduced: First release not established; documented by OpenOffice.org 3.3.
• Supported in: Apache OpenOffice 4.1.16; no final supported release is established.
• Scope: English desktop Calc, Analysis add-in compatibility identity and semicolon-separated formulas.
• Checked: October 14, 2026. One ordinary English-name formula was directly entered and recalculated in 4.1.16 on Linux x86-64, Build 9816. The table contains independent references; the failed generated-ODF import is separate.

ISEVEN_ADD returns numeric 1 for an even integer and numeric 0 for an odd integer through the Analysis add-in interface. It is distinct from the core ISEVEN function. The implementation tests the low binary bit of its signed integer argument. Release implementation.

=ISEVEN_ADD(Number)

• Number: integer to classify.

Exactly one argument is declared. The add-in receives a signed 32-bit integer and returns a signed 32-bit integer. Use ordinary integers when reproducing the tested contract; fractional and out-of-range conversion are not covered here.

These values follow the stated mathematical formulas and the inspected integer-input contract. They are not presented as eight native executions. Results are rounded to twelve decimal places where needed.

The integer examples 0, 2, −2 and 100 return 1. Inputs 1, 7, −1 and −7 return 0. Zero is even because it is divisible by 2 with no remainder. A negative sign does not change whether an integer is even.

For a sequence of integer identifiers, numeric 1/0 results can be used as indicators. Adding the indicators counts even identifiers, but the formula does not validate whether the identifiers were intentionally integers before they reached the add-in interface.

For every listed integer k, the two add-in parity functions satisfy ISEVEN_ADD(k)+ISODD_ADD(k)=1. This follows independently from integer parity: exactly one of even and odd applies. It is not evidence that arbitrary text or fractional values belong to the same contract.

The source expression tests nVal & 1 and returns an integer literal. Consequently, the saved result type matters: these examples establish numeric 1/0 values rather than a claim that every application stores them as Boolean TRUE/FALSE. Formatting a numeric one as a logical value does not change the underlying function identity.

The visible integer interface does not itself document every spreadsheet-to-integer conversion rule. The reference rows deliberately use small exact integers, including both signs. Fractions, empty cells, text, errors and values outside the signed 32-bit range were not executed.

If replacing an imported compatibility formula with core ISEVEN, verify the core function’s conversion and result conventions separately. A matching result for 2 is not a general compatibility proof. Keep the add-in suffix when identifying the original formula in an audit or migration.

The directly entered English formula =ISEVEN_ADD(-2) produced the saved result 1. The English entry and its serialized identity were reviewed together; an ODF canonical spelling alone cannot distinguish every core function from its compatibility add-in.

An earlier generated ODF used fully qualified Analysis service names. All eight import-path attempts for this function displayed #NAME?, despite passing recalculation controls. Those errors do not establish that the English function is unsupported. They also do not count as successful reference-case executions. Do not copy a fully qualified storage name into a normal formula expecting it to behave like the English name.

ISEVEN, ISODD, mod.

• Function-specific release implementation
• Separate English and ODF add-in identities

Only the single direct-entry case above is successful native function evidence in this guide. The remaining table values and explanatory identities are independently calculated. The failed generated-ODF workbook, including its informational attribute-load warning, is retained separately. No original XLSX execution, other locale, platform or release is implied.