Skip to content

Commit 80d937e

Browse files
jensmaurertkoeppe
authored andcommitted
[stmt.dcl] Clarify 'active' variables
They necessarily have automatic storage duration.
1 parent 1e1cb12 commit 80d937e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

source/statements.tex

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -943,14 +943,14 @@
943943
A variable with automatic storage duration\iref{basic.stc.auto}
944944
is \defnx{active}{variable!active} everywhere in the scope to which it belongs
945945
after its \grammarterm{init-declarator}.
946-
947-
\pnum
948946
\indextext{initialization!jump past}%
949947
\indextext{\idxcode{goto}!initialization and}%
950948
Upon each transfer of control (including sequential execution of statements)
951949
within a function from point $P$ to point $Q$,
952-
all variables that are active at $P$ and not at $Q$ are destroyed in the reverse order of their construction.
953-
Then, all variables that are active at $Q$ but not at $P$ are initialized in declaration order;
950+
all variables with automatic storage duration
951+
that are active at $P$ and not at $Q$ are destroyed in the reverse order of their construction.
952+
Then, all variables with automatic storage duration
953+
that are active at $Q$ but not at $P$ are initialized in declaration order;
954954
unless all such variables have vacuous initialization\iref{basic.life},
955955
the transfer of control shall not be a jump.
956956
\begin{footnote}

0 commit comments

Comments
 (0)