attribute when used from C++ under all compilers.

called from Fortran and was wrongly declared:

which some package maintainers wish to avoid.

Note that the last three are keywords in C23 and C++11 so cannot be

avoided entirely.  However, with commonly-used compilers they can be

masked by a macro of the same name, often with a warning.

contains very experimental annotations for more clearly

identifying the API status of C entry points. These annotations

are used to produce indices for API, experimental API, and

embedded API entry points in the rendered versions.  This is very

preliminary and may be dropped if a better approach emerges.

Also for Fortran-callable entry points which are part of the API.

away from using non-API endpoints. This section will continue to

be updated as work on clarifying and tightening the C API

arguments are valid and should be used instead of

closure components.  The existing functions

Further non-API entry points have been added to those reported

in public header files will be removed in the near future, and

Additional non-API entry points have been added to those

s, consistent with counting items in the

the current evaluation state and proceeding through the

of the requested entry from the call stack.

has been revised to describe the remapped

used from C code (but is recommended for new C code).

long-deprecated/obsolete Fortran features reported by

UTF-8 or Latin-1 strings in character data.  Set environment

with a true value for environment variable

check demo scripts analogously to tests.  This includes a check

for undeclared package dependencies: it can also be enabled

separately by setting the environment variable

on platforms with sufficient support for

formats correctly also in cases where rounding

up, e.g., from 9.96 to 10 needs more digits; thanks to

Printing matrices (typically with many rows and or columns)

now also omits columns when desirable according to option

no longer explicitly coerces results from

Dirk Eddelbuettel; also fixes more cases, notably

signal an error instead of invalidating ops relying on a finite