Merge branch 'barry/2026-01-13/ftn-generation-for-context-functions' into 'main'

Fortran generation of interface definitions for functions that take and return context variables (void *ctx and PetC

Merge branch 'barry/2026-01-13/ftn-generation-for-context-functions' into 'main'

Fortran generation of interface definitions for functions that take and return context variables (void *ctx and PetCtx ctx)

See merge request petsc/petsc!8956

show more ...

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 ...

Merge branch 'MarDiehl/use-bool-instead-of-enum' into 'main'

use bool instead of enum

See merge request petsc/petsc!8528

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 ...

Merge remote-tracking branch 'origin/release'

Merge branch 'jolivet/fix-docstrings' into 'release'

Fix wrong docstrings

See merge request petsc/petsc!8589

Fix wrong docstrings

Merge branch 'barry/2024-04-13/fix-sowing-strings' into 'main'

Update PETSc to use sowing bfort that handles string arguments and PETSC_NULL_INT

See merge request petsc/petsc!7480

sowing: update bfort to version that handles string arguments

and sync with version fixes in sowing

Merge remote-tracking branch 'origin/release'

Merge branch 'barry/2023-11-01/docs-kspcomputeeigenvalues/release' into 'release'

Fix manual pages in ksp/interface files

See merge request petsc/petsc!6988

Fix capitalization of fortran

Commit-type: housekeeping

Merge branch 'jacobf/2023-08-09/linter-detect-static-function-candidates' into 'main'

Linter detect possible static functions

See merge request petsc/petsc!6796

Linter now tries to detect functions that could be static, and makes it so.

Merge branch 'jacobf/2023-07-18/linter-documentation' into 'main'

Document Linter

See merge request petsc/petsc!6734

Document linter and add type hints

Merge branch 'jacobf/2023-07-19/lint-apply-ts' into 'main'

Manual linter fixes: ts

See merge request petsc/petsc!6736

Fix bug in self-referential docstring checks

Merge branch 'jacobf/2023-06-30/enable-doc-lint' into 'main'

Enable docs linting

See merge request petsc/petsc!6667

Crudely handle variadic functions for now

TODO blindy assume that macro arguments are OK for now

Fix flip-flop in seealso alignment check

Make header guessing slightly more robust against 'for example'-style false positives

Fix indent-check not being made when switching sections

Clearly describe how to document function pointer parameters if they are detected (and
missing docstring args are as well)