Docs/defensive-coding-guide
2
0
Fork 0
Code Issues 3 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Fix accidental formatting in monospaced text #27

Merged
ryanlerch merged 1 commit from literal-monospace-conversion into master 2025-03-25 14:40:52 +00:00
Conversation 3 Commits 1 Files changed 3 +6 -6
3 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

4
modules/ROOT/pages/programming-languages/C.adoc
View file

@ -770,7 +770,7 @@ are not implemented as inline functions or preprocessor macros.
The compiler lacks knowledge of such wrappers outside the
translation unit which defines them, which means that some
optimizations and security checks are not performed. Adding
`__attribute__` annotations to function
`+__attribute__+` annotations to function
declarations can remedy this to some extent, but these
annotations have to be maintained carefully for feature parity
with the standard implementation.
@ -788,7 +788,7 @@ propagate its return value, your wrapper should be declared
with `warn_unused_result` as well.
* Duplicating the buffer length checks based on the
`__builtin_object_size` GCC builtin is
`+__builtin_object_size+` GCC builtin is
desirable if the wrapper processes arrays. (This
functionality is used by the
`-D_FORTIFY_SOURCE=2` checks to guard

2
modules/ROOT/pages/programming-languages/Java.adoc
View file

@ -375,7 +375,7 @@ necessarily constant during the lifetime of your JNI module.
Storing it in a global variable is therefore incorrect.
Particularly if you are dealing with callbacks, you may have to
store the pointer in a thread-local variable (defined with
`__thread`). It is, however, best to avoid the
`+__thread+`). It is, however, best to avoid the
complexity of calling back into Java code.
Keep in mind that C/C++ and Java are different languages,

6
modules/ROOT/pages/tasks/Tasks-Processes.adoc
View file

@ -266,8 +266,8 @@ variables.
The Autoconf macro `AC_GNU_SOURCE` ensures this.
* Check for the presence of the `secure_getenv`
and `__secure_getenv` function. The Autoconf
directive `AC_CHECK_FUNCS([__secure_getenv secure_getenv])`
and `+__secure_getenv+` function. The Autoconf
directive `+AC_CHECK_FUNCS([__secure_getenv secure_getenv])+`
performs these checks.
* Arrange for a proper definition of the
@ -286,7 +286,7 @@ restrictions or cause a privileged process to behave in an
unexpected way.
Either the `secure_getenv` function or the
`__secure_getenv` is available from GNU libc.
`+__secure_getenv+` is available from GNU libc.
[[ex-Defensive_Coding-Tasks-secure_getenv]]
.Obtaining a definition for `secure_getenv`