id summary reporter owner description type status priority milestone component version severity resolution keywords cc 533 clarification of psTrace()'s functionality requested by MHPCC jhoblitt David.Robbins@… "From: David Robbins Date: Tue, 20 Sep 2005 16:28:47 -1000 To: Joshua Hoblitt Subject: RE: [ps-ipp-dev] pslib api delta report for 2005-09-19 Josh, Sounds good. I think a good portion of what was supposed to be 'cleaned up' has been done. If it's not too much trouble, my suggestion on the distribution of these reports would be upon request/demand. Meaning, if you guys have things you'd like to see done, feel free to send one. Otherwise, I would be happy requesting a copy when needed on our side. This document is most useful before and after each new SDRS release so that would be a good fallback schedule. On another note, it appears that we have had many different people working on psTrace throughout, but apparently Robert Lupton was the original author. The way that the function (psTrace) currently operates seems somewhat different than the SDRS. That is, there is essentially an additional argument for ""formatting"" the output. The SDRS has the function prototype listed as- void psTrace(const char *facil, int level, const char *format, ...); Currently, it seems to function more like, void psTrace(const char *facil, int level, const char *indent, const char *format, ...); Where indent is usually "" "" and is multiplied by the level. i.e., if indent=1 space and the level=3, the output is indented 3 spaces. Or for indent=2, level=3, 6 spaces, and so on... Consequently, I wanted to see whether the indenting is something that should be removed or is a desired component of this function. We're kind of assuming that the current state is incorrect. Please advise. -Dave" defect closed high PSLib SDRS unspecified normal fixed rhl@…