An 'undefined' page is any page that has been linked to from within Confluence, but that does not yet exist.
| Undefined Page |
Linked From |
FIO04-C. Detect and handle input and output errors
|
VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() >
Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait()
(SEI CERT C Coding Standard)
void FIO33-C. Detect and handle input output errors resulting in undefined behavior >
Re: void FIO33-C. Detect and handle input output errors resulting in undefined behavior
(SEI CERT C Coding Standard)
VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() >
Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait()
(CInternalTest)
void FIO33-C. Detect and handle input output errors resulting in undefined behavior >
Re: void FIO33-C. Detect and handle input output errors resulting in undefined behavior
(CInternalTest)
void FIO33-C. Detect and handle input output errors resulting in undefined behavior >
Re: void FIO33-C. Detect and handle input output errors resulting in undefined behavior
(SEI CERT C Coding Standard)
|
|
FIO18-CPP. Never expect write() to terminate the writing process at a null character
|
FIO18-C. Never expect fwrite() to terminate the writing process at a null character >
Re: FIO18-C. Never expect fwrite() to terminate the writing process at a null character
(SEI CERT C Coding Standard)
|
|
FIO31-C. Do not open a file that is already open
|
POS38-C. Beware of race conditions when using fork and file descriptors >
Re: POS38-C. Beware of race conditions when using fork and file descriptors
(SEI CERT C Coding Standard)
|
|
FIO33-C. Detect and handle input output errors resulting in undefined behavior
|
VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() >
Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait()
(CInternalTest)
VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() >
Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait()
(SEI CERT C Coding Standard)
VOID FIO04-C. Detect and handle input and output errors >
Re: VOID FIO04-C. Detect and handle input and output errors
(SEI CERT C Coding Standard)
|
|
FIO43-C. Do not create temporary files in shared directories
|
VOID Temporary Files (TMP) >
Re: VOID Temporary Files (TMP)
(SEI CERT C Coding Standard)
MSC24-C. Do not use deprecated or obsolescent functions >
Re: MSC24-C. Do not use deprecated or obsolescent functions
(SEI CERT C Coding Standard)
VOID Temporary files must be removed before the program exits >
Re: VOID Temporary files must be removed before the program exits
(SEI CERT C Coding Standard)
|
|
FLP02-C. Avoid using floating point numbers when precise computation is needed
|
VOID Take granularity into account when comparing floating point values >
Re: VOID Take granularity into account when comparing floating point values
(CInternalTest)
VOID Take granularity into account when comparing floating point values >
Re: VOID Take granularity into account when comparing floating point values
(SEI CERT C Coding Standard)
|
|
FLP03-C. Detect and handle floating point errors
|
DCL00-C. Const-qualify immutable objects >
Re: DCL00-C. Const-qualify immutable objects
(SEI CERT C Coding Standard)
|
|
FLP33-C. Convert integers to floating point for floating point operations
|
FLP30-C. Do not use floating-point variables as loop counters >
Re: FLP30-C. Do not use floating-point variables as loop counters
(SEI CERT C Coding Standard)
|
|
First attempt wrote the preformatted box inline, and then appeared with 'unknown macro' in the Wiki markup.\
|
EXP07-C. Do not diminish the benefits of constants by assuming their values in expressions >
Re: EXP07-C. Do not diminish the benefits of constants by assuming their values in expressions
(SEI CERT C Coding Standard)
|
|
I do know the ISO standard prohibits taking the sizeof a function. However, I was wondering if the prohibition was on taking the sizeof +any+ pointer symbol. Clearly, however, I now see the guideline does permit taking the sizeof a function po
|
VOID EXP01-C. Do not take the size of a pointer to determine the size of the pointed-to type >
Re: VOID EXP01-C. Do not take the size of a pointer to determine the size of the pointed-to type
(SEI CERT C Coding Standard)
|
|
I tried using literal XML notation; it doesn't appear in the Wiki output.\
|
PRE04-C. Do not reuse a standard header file name >
Re: PRE04-C. Do not reuse a standard header file name
(SEI CERT C Coding Standard)
|
|
INT17-C. Do not make assumptions about representation of signed integers
|
Page: VOID INT20-C. Use the type ptrdiff_t when storing the difference of two pointers
(CInternalTest)
Page: VOID INT20-C. Use the type ptrdiff_t when storing the difference of two pointers
(SEI CERT C Coding Standard)
|
|
INT_MIN + 49\
|
INT01-C. Use rsize_t or size_t for all integer values representing the size of an object >
Re: INT01-C. Use rsize_t or size_t for all integer values representing the size of an object
(SEI CERT C Coding Standard)
|
|
INT_MIN, INT_MAX
|
INT01-C. Use rsize_t or size_t for all integer values representing the size of an object >
Re: INT01-C. Use rsize_t or size_t for all integer values representing the size of an object
(SEI CERT C Coding Standard)
|
|
INT_MIN, INT_MAX\
|
INT08-C. Verify that all integer values are in range >
Re: INT08-C. Verify that all integer values are in range
(SEI CERT C Coding Standard)
|
|
INT_MIN/2, INT_MAX/2
|
INT08-C. Verify that all integer values are in range >
Re: INT08-C. Verify that all integer values are in range
(SEI CERT C Coding Standard)
|
|
INT_MIN\
|
INT01-C. Use rsize_t or size_t for all integer values representing the size of an object >
Re: INT01-C. Use rsize_t or size_t for all integer values representing the size of an object
(SEI CERT C Coding Standard)
|
|
format specifier\
|
FLP04-C. Check floating-point inputs for exceptional values >
Re: FLP04-C. Check floating-point inputs for exceptional values
(SEI CERT C Coding Standard)
|
|
i\
|
MSC07-C. Detect and remove dead code >
Re: MSC07-C. Detect and remove dead code
(SEI CERT C Coding Standard)
|
|
in\
|
FLP30-C. Do not use floating-point variables as loop counters >
Re: FLP30-C. Do not use floating-point variables as loop counters
(SEI CERT C Coding Standard)
|
|
FIO04-C. Detect and handle input and output errors
|
VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() >
Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait()
(SEI CERT C Coding Standard)
void FIO33-C. Detect and handle input output errors resulting in undefined behavior >
Re: void FIO33-C. Detect and handle input output errors resulting in undefined behavior
(SEI CERT C Coding Standard)
VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() >
Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait()
(CInternalTest)
void FIO33-C. Detect and handle input output errors resulting in undefined behavior >
Re: void FIO33-C. Detect and handle input output errors resulting in undefined behavior
(CInternalTest)
void FIO33-C. Detect and handle input output errors resulting in undefined behavior >
Re: void FIO33-C. Detect and handle input output errors resulting in undefined behavior
(SEI CERT C Coding Standard)
|
|
FIO18-CPP. Never expect write() to terminate the writing process at a null character
|
FIO18-C. Never expect fwrite() to terminate the writing process at a null character >
Re: FIO18-C. Never expect fwrite() to terminate the writing process at a null character
(SEI CERT C Coding Standard)
|
|
FIO31-C. Do not open a file that is already open
|
POS38-C. Beware of race conditions when using fork and file descriptors >
Re: POS38-C. Beware of race conditions when using fork and file descriptors
(SEI CERT C Coding Standard)
|
|
FIO33-C. Detect and handle input output errors resulting in undefined behavior
|
VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() >
Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait()
(CInternalTest)
VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() >
Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait()
(SEI CERT C Coding Standard)
VOID FIO04-C. Detect and handle input and output errors >
Re: VOID FIO04-C. Detect and handle input and output errors
(SEI CERT C Coding Standard)
|
|
FIO43-C. Do not create temporary files in shared directories
|
VOID Temporary Files (TMP) >
Re: VOID Temporary Files (TMP)
(SEI CERT C Coding Standard)
MSC24-C. Do not use deprecated or obsolescent functions >
Re: MSC24-C. Do not use deprecated or obsolescent functions
(SEI CERT C Coding Standard)
VOID Temporary files must be removed before the program exits >
Re: VOID Temporary files must be removed before the program exits
(SEI CERT C Coding Standard)
|
|
FLP02-C. Avoid using floating point numbers when precise computation is needed
|
VOID Take granularity into account when comparing floating point values >
Re: VOID Take granularity into account when comparing floating point values
(CInternalTest)
VOID Take granularity into account when comparing floating point values >
Re: VOID Take granularity into account when comparing floating point values
(SEI CERT C Coding Standard)
|
|
FLP03-C. Detect and handle floating point errors
|
DCL00-C. Const-qualify immutable objects >
Re: DCL00-C. Const-qualify immutable objects
(SEI CERT C Coding Standard)
|
|
FLP33-C. Convert integers to floating point for floating point operations
|
FLP30-C. Do not use floating-point variables as loop counters >
Re: FLP30-C. Do not use floating-point variables as loop counters
(SEI CERT C Coding Standard)
|
|
First attempt wrote the preformatted box inline, and then appeared with 'unknown macro' in the Wiki markup.\
|
EXP07-C. Do not diminish the benefits of constants by assuming their values in expressions >
Re: EXP07-C. Do not diminish the benefits of constants by assuming their values in expressions
(SEI CERT C Coding Standard)
|
|
I do know the ISO standard prohibits taking the sizeof a function. However, I was wondering if the prohibition was on taking the sizeof +any+ pointer symbol. Clearly, however, I now see the guideline does permit taking the sizeof a function po
|
VOID EXP01-C. Do not take the size of a pointer to determine the size of the pointed-to type >
Re: VOID EXP01-C. Do not take the size of a pointer to determine the size of the pointed-to type
(SEI CERT C Coding Standard)
|
