public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10025] wildcards lose when embedded in conditional %( %) expressions
Date: Tue, 18 May 2010 20:07:00 -0000	[thread overview]
Message-ID: <20100518044302.32496.qmail@sourceware.org> (raw)
In-Reply-To: <20090402151723.10025.eteo@redhat.com>


------- Additional Comments From fche at redhat dot com  2010-05-18 04:43 -------
> I thought about peeking ahead to the next token and merging them, but you also
> need to make sure that we don't merge them when they truly are two tokens, like
> "foo *" (which in a probe point should be a syntax error).

Maybe we can relax that 'should be a syntax error' thing and accept it anyway.
(This could be a stap version-sensitive parser change if desired).  So the
idea would be to do token-pasting within parse_probe_point only, gluing
together tok_identifier / tok_keyword / selected-tok_operator into a single
synthetic tok_identifier for the probe_point component.  If we want to be
selective to the presence of whitespace, one not-too-gross way may be to
have a new flag within tokens, set by the lexer, to indicate that some
whitespace was skipped since the last token.  We'd stop the gluing upon
such a token.


-- 


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

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

  parent reply	other threads:[~2010-05-18  4:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 15:17 [Bug translator/10025] New: Problem with conditional preprocessing eteo at redhat dot com
2009-04-02 15:40 ` [Bug translator/10025] " eteo at redhat dot com
2009-04-02 16:13 ` [Bug translator/10025] wildcards lose when embedded in conditional %( %) expressions fche at redhat dot com
2010-05-13 18:02 ` fche at redhat dot com
2010-05-13 19:07 ` dsmith at redhat dot com
2010-05-13 21:04 ` jistone at redhat dot com
2010-05-18 20:07 ` fche at redhat dot com [this message]
2010-05-20 19:06 ` jistone at redhat dot com
2010-05-20 19:12 ` jistone at redhat dot com
2010-05-20 19:22 ` fche at redhat dot com
2010-05-21 19:33 ` fche at redhat dot com
2010-05-21 19:40 ` jistone at redhat dot com
2010-05-24 15:54 ` jistone at redhat dot com

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=20100518044302.32496.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@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).