This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug documentation/11224] setting module arguments needs to be tested/documented
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 26 Jan 2010 22:41:51 -0000
- Subject: [Bug documentation/11224] setting module arguments needs to be tested/documented
- References: <20100126221502.11224.dsmith@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2010-01-26 22:41 -------
> I see your point, but I also wonder if we lose something here. For instance,
> assume the following pseudo-script:
>
> global debug=0
> probe PROBE_POINT {
> if (debug) {
> # print interesting debug information
> }
> }
>
> This allows a default 'debug' value of 0, which we then can override from the
> command line using module arguments when we want the extra debug output.
One doesn't have to explicitly initialize anything to 0. By leaving out
the =0, in my scheme one would permit runtime overrides.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11224
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.