[Bug translator/19136] New: "private" keyword for tapsets

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

https://sourceware.org/bugzilla/show_bug.cgi?id=19136

            Bug ID: 19136
           Summary: "private" keyword for tapsets
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: fche at redhat dot com
  Target Milestone: ---

For namespace hygiene purposes, it would be nice for tapsets (and perhaps the
end-user script too) to be able to designate globals and functions as private
(... maybe probe point aliases too?)

This would affect the parser (accepting a new keyword "private", conditionally
on systemtap compatibility version 3.0+), passing that as flag onto the vardecl
/ functiondecl.  During pass-2 symbol resolution (elaborate.cxx
semantic_pass_symbols(), the flag would have to be checked when matching names
to decls.

See also bug #11347.  We solved that in another way sort of by addition of the
/* guru */ marker to embedded-C.  This could strengthen/replace that hack.

See also bug #13721.  There, tapset locals and end-user-script globals were in
conflict.  If the end-user-script global were marked private, it would not
have.

See also bug #10607.  Private flagged variables could be exempt from -G
processing.

-- 
You are receiving this mail because:
You are the assignee for the bug.