Re: proposal for ICU tracing

Carl,

OK, I missed the connection between the storage type and optionality of the
function.
If so, that's great.
I'll have to look at TLS to see how that happens.
Thanks
tex

"Carl W. Brown" wrote:
> 
> Tex,
> 
> > There is a speed advantage to the wrapper approach if it can be
> > turned on for
> > some callers and not others, compared to the "on for all/off for
> > all approach"
> > of putting it in the lower layers.
> > The speed cost is more than the if statement, as it includes the
> > logging of
> > calls the user is not interested in- so there is the cost of
> > logging and the
> > cost of filtering or sorting thru the uninteresting data.
> 
> This is the point of putting the trace controls in TLS.  Usually in most
> cases it is only specific events that you want to trace.  Selectively
> tracing when the thread is making certain call or under special
> circumstances will dramatically reduce the overhead without having to
> reengineer every API to pass trace controls which would be a significant
> rewrite of ICU.
> 
> Carl
> 
> _______________________________________________
> icu mailing list
> [email protected]
> http://oss.software.ibm.com/developerworks/oss/mailman/listinfo/icu

-- 
-------------------------------------------------------------
Tex Texin   cell: +1 781 789 1898   mailto:[email protected]
Xen Master                          http://www.i18nGuy.com
                         
XenCraft		            http://www.XenCraft.com
Making e-Business Work Around the World
-------------------------------------------------------------