From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-14225-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 20222 invoked by alias); 9 Nov 2009 13:22:13 -0000
Received: (qmail 20044 invoked by uid 48); 9 Nov 2009 13:22:00 -0000
Date: Mon, 09 Nov 2009 13:22:00 -0000
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20091109132200.10927.mjw@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug documentation/10927] New: do-while statement unimplemented, but documented
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2009-q4/txt/msg00466.txt.bz2

doc/langref.tex:

\subsection{do}
\index{do}
The \texttt{do} statement has the same syntax and semantics as in C.

\begin{vindent}
\begin{verbatim}
do STMT while (EXP)
\end{verbatim}
\end{vindent}

But parse.cxx (parser::parse_statement):
  // XXX: "do/while" statement?

$ stap -v -e 'probe begin { do { log("nothing"); } while (0); }'
WARNING: read-only local variable 'do' : identifier 'do' at <input>:1:15
 source: probe begin { do { log("nothing"); } while (0); }
                       ^
WARNING: eliding unused variable 'do': identifier 'do' at :1:15
 source: probe begin { do { log("nothing"); } while (0); }

-- 
           Summary: do-while statement unimplemented, but documented
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: documentation
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: mjw at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=10927

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.