On Fri, Feb 01, 2008 at 12:11:52AM -0800, Paul van den Bogaard wrote: > Why was this header file creation invented given that the manual, in > the chapter of statically defined probes for applications, only > mentions the macro's DTRACE_PROBExxx?
The header file generation was developed both to support is-enabled probes, and to add a better interface. The Solaris Dynamic Tracing Guide will be updated when I get a chance. If anyone would like to take a whack, here's the link to the wiki; send out a draft: http://wikis.sun.com/display/DTrace/Statically+Defined+Tracing+for+User+Applications > I have the impression that the "misunderstanding" starts with > allowing the hyphen in probe names: are there any other programming or > scripting languages that allow a math symbol in a variable name? But > ala that decision has been made. Many would consider the hyphen to be more typographical than mathematical, but I don't know whether other langages alow that as part of a lexical object. > "It would be tricky to..." is your final remark. Could you elaborate > a little here, since the core part of the code is working as Trond also > p ointed out. It is just the "religions" "One underscore looks better in > macros" vs "Do not translate in an irreversable way" It would be tricky by which I mean to say impossible to change by default as that would break existing consumers. > by default stick to the current behaviour. I that irreversable way is > not wanted use an option (yet another one) with dtrace that "just" > translates the macro names keeping double underscores in place. One could add such an option to dtrace(1M), sure. I'm not sure it would represent a real improvement and might be confusing to add another way to do the same thing. You could probably hack up my old dheadgen.pl to do what you want. http://www.opensolaris.org/jive/thread.jspa?messageID=132638𠘞 - ahl -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl _______________________________________________ dtrace-discuss mailing list [email protected]
