Remove the last of the use of horizontal lines --- as seperators. With modern code development systems they are not needed and just an eye-sore

Add automatic generated fortran support for setting and returning contexts

Major cleanup of the code for setting and returning application (previously called user) contexts
- PetscCtx ctx is now t

Add automatic generated fortran support for setting and returning contexts

Major cleanup of the code for setting and returning application (previously called user) contexts
- PetscCtx ctx is now the standard for passing in contexts
- PetscCtxRt ctx is the standard for passing out contexts, including context destroy routines based on PetscCtxDestroyFn

Both of these are typedef to void*

Also removed most use of user and userctx for context arguments now consistently named ctx

Improved documentation on PetscCtx and PetscCtxRt and on how to use contexts (including getting them) from Fortran

show more ...

Fortran: enforce lower case keywords and operators

also fixed occasional capitals in used modules with the help of @prj-

checkbadSource: enforce proper style in makefiles

Run fprettify

use standard bool instead of enum

PetscBool is equivalent to _Bool/bool in C

For C standards prior to C23, true = 1 and false = 0 are defined in <stdbool.h>.
For C23, true and false are real keywor

use standard bool instead of enum

PetscBool is equivalent to _Bool/bool in C

For C standards prior to C23, true = 1 and false = 0 are defined in <stdbool.h>.
For C23, true and false are real keywords.

The Fortran equivalent is logical(C_BOOL) with C_BOOL from
ISO_C_binding.

The C and the C++ standard do not specify the size of Booleans, but they
typically have a size of 1 Byte with b00000000 for false and b00000001 for true.
When using compilers from the same vendor, it is sane to assume that
_Bool/bool in C and bool in C++ are fully compatible. But that is not
guaranteed by the standards

show more ...

ensure that Fortran Bool is interoperable

The kind C_BOOL for logical from ISO_C_binding only defines the size of
the logical as 1 Byte. It does not define which values (bit patterns) are
used to en

ensure that Fortran Bool is interoperable

The kind C_BOOL for logical from ISO_C_binding only defines the size of
the logical as 1 Byte. It does not define which values (bit patterns) are
used to encode true and false. In stdbool.h from C, true is defined as 1
and false as 0, but these values are not guaranteed by the Fortran standard.

There are (at least) two contemporary Fortran compilers that use a
difference convention: Intel Fortran (ifort and ifx) and NVIDIA Fortran
(nvfortran, former PGI). Both represent true as all bits set, i.e. -1 for
a signed integer or 255 for an unsigned integer.

Intel Fortran can be made interoperable with the "-standard-semantics" or
"-fpscomp logicals". The latter is now set by default to ensure
interoperability while avoiding effects such as modified name mangling
rules and performance degradations due to the former.

NVIDIA Fortran can be made interoperable with the "-Munixlogical" flag.
This is set manually in the "linux-cuda-single-cxx" pipeline. This is
now set by default.

show more ...