From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: <systemtap@sourceware.org>
Subject: RE: Global constants
Date: Mon, 13 Feb 2006 22:12:00 -0000 [thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC06654CE1@scsmsx403.amr.corp.intel.com> (raw)
Frank Ch. Eigler wrote:
> That would still burden the tapset programmer to add the necessary
> %{ #include <linux/foo.h> %}'s to define all those macros.
Good point.
> [...]
> This could be a plausible solution for bug #1304 (with the addition of
> some type data). But I would like to aim for something that can be
> set at startup time rather than compile time. That would be an
> element of bug #2208, where precompiled probe modules may be reused.
> That in turn is more useful if they can be parametrized.
Now that I've looked at those bug #s, I tend to agree - a more general
solution for script parameters is needed. It's still possible to "fake"
parameters with macros, but given the limitations I don't think we need
more language features around this idea.
Josh
next reply other threads:[~2006-02-13 22:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 22:12 Stone, Joshua I [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-13 21:50 Stone, Joshua I
2006-02-13 23:50 ` Frank Ch. Eigler
2006-02-13 20:36 Stone, Joshua I
2006-02-13 21:05 ` Frank Ch. Eigler
2006-02-13 20:13 Stone, Joshua I
2006-02-13 20:46 ` Frank Ch. Eigler
2006-02-13 17:39 Mark McLoughlin
2006-02-13 19:28 ` Frank Ch. Eigler
2006-02-13 19:40 ` Martin Hunt
2006-02-13 20:10 ` Frank Ch. Eigler
2006-02-13 20:20 ` Mark McLoughlin
2006-02-13 20:14 ` Mark McLoughlin
2006-02-13 20:22 ` Martin Hunt
2006-02-13 20:44 ` Mark McLoughlin
2006-02-13 21:41 ` Martin Hunt
2006-02-14 8:27 ` Mark McLoughlin
2006-02-13 20:09 ` Mark McLoughlin
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=CBDB88BFD06F7F408399DBCF8776B3DC06654CE1@scsmsx403.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=fche@redhat.com \
--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: 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).