[Bug documentation/11224] setting module arguments needs to be tested/documented

["dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From dsmith at redhat dot com  2010-01-26 22:37 -------
(In reply to comment #1)
> Now that I think about it a little more, it makes more and more sense to
> have the translator detect that globals are initialized at the script
> level, and to block potential setting via module options (by omitting
> the MODULE_PARAM goo for those variables).  This would remove any ambiguity.  

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.

If we omit the MODULE_PARAM goo for 'debug', we wouldn't be able to override the
default value from the command line (without recompiling).



-- 


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.