orthonym.opsin_capabilities

Note

Internal API. Names and behaviour may change between releases.

What the OPSIN in use can read.

OPSIN 2.9.0 reads neither phane names nor halogen “-uide” anions with substituents (diphenyliodanuide); OPSIN’s main branch reads both. A name of such a form can be checked by a round trip only when the OPSIN in use reads it, so a producer of such names asks here before it offers one. Nothing in the engine calls this yet.

The release jar (the pinned, checksummed 2.9.0) is known to read neither and is not probed. Any other jar – built from OPSIN’s main branch (ORTHONYM_OPSIN) or given by ORTHONYM_OPSIN_JAR – is probed once with two names through the in-process OPSIN, the entry point of the validity gate, and the answer is kept per jar (and, for a built jar, in its .json file). A probe that cannot be answered (no in-process OPSIN, a busy JVM) reads as “cannot” for that call only and is not kept, so one failed call never switches a capability off for the rest of the process.

orthonym.opsin_capabilities.opsin_capabilities()

{"phane": bool, "halogen_uide": bool} for the OPSIN this process uses.

orthonym.opsin_capabilities.phane_enabled()

True when the OPSIN in use reads phane names.