From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Stone, Joshua I" <joshua.i.stone@intel.com>
Cc: systemtap@sources.redhat.com
Subject: Re: command line arguments
Date: Fri, 24 Feb 2006 01:00:00 -0000 [thread overview]
Message-ID: <20060224010025.GF20902@redhat.com> (raw)
In-Reply-To: <CBDB88BFD06F7F408399DBCF8776B3DC067B2AFB@scsmsx403.amr.corp.intel.com>
Hi -
> It would indeed be nice if $N could be dynamically be typed, especially
> since the other $target variables are, but I can see how this would be
> hard.
That's the heuristic I was talking about. One problem is that several
places like probe point functors (.statement(), .function()) accept
*both* string or number literals.
> The @ is ok, but it doesn't really say "string" to me. Perhaps a
> single-quote or backquote might be better - '1 or `1?
Or perhaps a backslash, as in regexps.
> Another option is to allow expansion of $N within string literals [...]
> # stap -e 'probe kernel.function("$1") { print($2) }' sys_open 4
But then normal dollar signs would have to be quoted.
- FChE
next prev parent reply other threads:[~2006-02-24 1:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 23:41 Stone, Joshua I
2006-02-24 1:00 ` Frank Ch. Eigler [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-23 22:42 Frank Ch. Eigler
2006-02-24 5:52 ` Martin Hunt
2006-02-24 12:24 ` Frank Ch. Eigler
2006-02-24 18:44 ` Martin Hunt
2006-02-25 21:38 ` Frank Ch. Eigler
2006-02-27 20:34 ` Martin Hunt
2006-02-24 13:42 ` Daniel P. Berrange
2006-02-24 15:51 ` Frank Ch. Eigler
2006-02-24 20:59 ` Roland McGrath
2006-02-24 21:22 ` Frank Ch. Eigler
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=20060224010025.GF20902@redhat.com \
--to=fche@redhat.com \
--cc=joshua.i.stone@intel.com \
--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).