Repository navigation
Pair a Doxygen block with a definition whose signature a guard chooses - #223
Merged
estebanzimanyi merged 1 commit intoOct 31, 2026
Conversation
A guard may sit between the return-type line and the name of a definition, choosing between two spellings of one signature, or inside its parameter list. basetype_in in meos/src/temporal/type_in.c marks its end parameter UNUSED in the build that does not read it, and skiplist_splice in meos/src/temporal/skiplist.c its sktype parameter. The definition pattern every @PARAM reader shares steps over the guard after the return type and over the #else or #elif spellings and the closing #endif before the body, and keeps the first spelling as the parameters. On MobilityDB master 3c5baef2b3 the readers pair basetype_in and skiplist_splice with their own blocks: basetype_in answers through its result out parameter, parse_mfjson_coord and skiplist_values, which follow them, keep their own blocks and document no parameter, and every other function the readers derive is unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A guard may sit between the return-type line and the name of a definition,
choosing between two spellings of one signature, or inside its parameter
list. basetype_in in meos/src/temporal/type_in.c marks its end parameter
UNUSED in the build that does not read it, and skiplist_splice in
meos/src/temporal/skiplist.c its sktype parameter. The definition pattern
every @PARAM reader shares steps over the guard after the return type and
over the #else or #elif spellings and the closing #endif before the body,
and keeps the first spelling as the parameters.
On MobilityDB master 3c5baef2b3 the readers pair basetype_in and
skiplist_splice with their own blocks: basetype_in answers through its
result out parameter, parse_mfjson_coord and skiplist_values, which follow
them, keep their own blocks and document no parameter, and every other
function the readers derive is unchanged.