public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sources.redhat.com
Subject: src ./ChangeLog ./Makefile.in ./config.in ./co ...
Date: Thu, 02 Jun 2005 19:43:00 -0000 [thread overview]
Message-ID: <20050602194356.14609.qmail@sourceware.org> (raw)
CVSROOT: /cvs/systemtap
Module name: src
Changes by: fche@sourceware.org 2005-06-02 19:43:56
Modified files:
. : ChangeLog Makefile.in config.in configure
configure.ac elaborate.cxx elaborate.h main.cxx
parse.cxx parse.h staptree.cxx staptree.h
translate.cxx translate.h
testsuite/parseko: seven.stp three.stp
testsuite/parseok: eight.stp
testsuite/semok: ten.stp
Added files:
testsuite/parseko: eight.stp
testsuite/parseok: nine.stp
testsuite/semko: eleven.stp
testsuite/semok: eleven.stp
Log message:
2005-06-02 Frank Ch. Eigler <fche@redhat.com>
Parse foreach construct. Added fuller copyright notices throughout.
* staptree.h (foreach_loop): New tree node type.
* staptree.cxx: Print it, visit it, love it, leave it.
* parse.cxx: Parse it.
(parse_stmt_block): Don't require ";" separators between statements.
(parse_array_in): Use [] as index group operator instead of ().
* elaborate.cxx (visit_foreach_loop): New code.
* translate.cxx: Slightly tighten errorcount/actioncount handling.
* main.cxx: Accept "-" as script file name standing for stdin.
(visit_arrayindex): Switch to simpler set_arity call.
* configure.ac: Generate DATE macro.
* Makefile.in, configure, config.in: Regenerated.
* testsuite/*: New/updated tests for syntax changes, foreach ().
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/ChangeLog.diff?cvsroot=systemtap&r1=1.13&r2=1.14
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/Makefile.in.diff?cvsroot=systemtap&r1=1.6&r2=1.7
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/config.in.diff?cvsroot=systemtap&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/configure.diff?cvsroot=systemtap&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/configure.ac.diff?cvsroot=systemtap&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/elaborate.cxx.diff?cvsroot=systemtap&r1=1.3&r2=1.4
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/elaborate.h.diff?cvsroot=systemtap&r1=1.1&r2=1.2
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/main.cxx.diff?cvsroot=systemtap&r1=1.1&r2=1.2
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/parse.cxx.diff?cvsroot=systemtap&r1=1.8&r2=1.9
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/parse.h.diff?cvsroot=systemtap&r1=1.7&r2=1.8
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/staptree.cxx.diff?cvsroot=systemtap&r1=1.10&r2=1.11
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/staptree.h.diff?cvsroot=systemtap&r1=1.9&r2=1.10
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/translate.cxx.diff?cvsroot=systemtap&r1=1.3&r2=1.4
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/translate.h.diff?cvsroot=systemtap&r1=1.1&r2=1.2
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/testsuite/parseko/eight.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/testsuite/parseko/seven.stp.diff?cvsroot=systemtap&r1=1.1&r2=1.2
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/testsuite/parseko/three.stp.diff?cvsroot=systemtap&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/testsuite/parseok/nine.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/testsuite/parseok/eight.stp.diff?cvsroot=systemtap&r1=1.1&r2=1.2
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/testsuite/semko/eleven.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/testsuite/semok/eleven.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/testsuite/semok/ten.stp.diff?cvsroot=systemtap&r1=1.1&r2=1.2
reply other threads:[~2005-06-02 19:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050602194356.14609.qmail@sourceware.org \
--to=fche@sourceware.org \
--cc=systemtap-cvs@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).