public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: serhei@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-48-g06219d6 Date: Fri, 20 Jul 2012 14:35:00 -0000 [thread overview] Message-ID: <20120720143513.15776.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, master has been updated via 06219d6fe60022c651206846090c8b5e1c96d652 (commit) from ca753ae54cf552ac578cc5d7414803e028e89c42 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 06219d6fe60022c651206846090c8b5e1c96d652 Author: Serguei Makarov <smakarov@redhat.com> Date: Fri Jul 20 10:26:40 2012 -0400 Fix '@operator' parsing -- strictly enforce use of '@' in identifiers. Generally, the language makes a policy of not allowing people to use '@' inside arbitrary identifiers. The new test case gives an example of behaviour that was still allowed by the parser's older scheme for preventing this. Identifiers beginning in '@' are now reclassified as tok_operator by the lexer. ----------------------------------------------------------------------- Summary of changes: parse.cxx | 39 +++++++++++++++++++++++++++-------- testsuite/parseko/at_operators.stp | 5 ++++ 2 files changed, 35 insertions(+), 9 deletions(-) create mode 100644 testsuite/parseko/at_operators.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-07-20 14:35 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=20120720143513.15776.qmail@sourceware.org \ --to=serhei@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --cc=systemtap@sourceware.org \ /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: linkBe 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).