QA·C Help - 1313

	1313	Executing 'goto %s' will cause local initialization to be skipped.

Miscellaneous		REFERENCE - ISO:C90-6.1.2.4 Storage Durations of Objects

A goto statement is jumping into a block of code where a local object is initialized. This initialization will be bypassed with the result that the object may be used when unset.

Message 1313 will be generated either at the goto statement or at the labelled statement to which it jumps, whichever is located first.

For example:


/*PRQA S 1-9999 ++*/
/*PRQA S 1313, 2752, 2962, 3311, 3312 --*/

extern int f1(int i, int n)
{
    if (n > 0)
        goto IN;

    if (i)
    {
        int j = 2;

        IN: n = j + 2;                  /* Message 1313 + 3311 + 2962 */

        goto OUT;
    }

    OUT: i = 2 + n;

    return i;
}

extern int f2(int i, int n)
{
    if (i)
    {
        int j = 2;

        IN: n = j + 2;

        goto OUT;
    }

    OUT: i = 2 + n;

    if (n > 0)
        goto IN;                        /* Message 1313 + 3312 + 2752 */

    return i;
}

See also:

2752 This 'construct' results in the function being too complex. Dataflow analysis continues with the next function.
2962 Apparent: Using value of uninitialized automatic object '%s'.
3311 [u] An earlier jump to this statement will bypass the initialization of local variables.
3312 [u] This goto statement will jump into a previous block and bypass the initialization of local variables.

Personality Groups | Glossary | Message Index

Contents