From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/6847] $$parms/$$vars should be $$*
Date: Mon, 18 Aug 2008 14:54:00 -0000 [thread overview]
Message-ID: <20080818145338.14585.qmail@sourceware.org> (raw)
In-Reply-To: <20080817132854.6847.mhiramat@redhat.com>
------- Additional Comments From fche at redhat dot com 2008-08-18 14:53 -------
> > The "$" *suffix* suggested in bug #3672 was done
> > specifically to avoid namespace collisions of the
> > kind you are looking for here.
>
> I think this also could simplify the syntax including bug #3672.
Let's just say they are opposing proposals.
> - one $ (ex. $var, $return): returns the value of var or return value.
> - two $ (ex. $$var, $$return, $$*): returns the values with variable names.
> - more than two $ (ex. $$$var, $$$*): returns the values ($ means the depth of
> nesting) with variable names.
One obstacle in this scheme's way is that there are material
differences betewen the various metavariables ($$return,
$$vars, $$parms, $$locals, and perhaps others in the future).
They can't all match "*". Further, there is interplay with
.return probes' optional saving of invocation-time variables.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6847
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-08-18 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-17 13:30 [Bug translator/6847] New: " mhiramat at redhat dot com
2008-08-17 15:26 ` [Bug translator/6847] " fche at redhat dot com
2008-08-17 20:07 ` mhiramat at redhat dot com
2008-08-17 20:12 ` mhiramat at redhat dot com
2008-08-18 14:54 ` fche at redhat dot com [this message]
2008-08-18 15:13 ` [Bug translator/6847] $$parms/$$vars should be $$* or $$%parms/$$%vars mhiramat at redhat dot com
2008-08-18 15:26 ` fche at redhat dot com
2008-08-28 16:09 ` mhiramat 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=20080818145338.14585.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).