Tracing

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Tracing

Luigi Ballabio
Hi all,
        a tracing facility is of course a useful one for debugging/
validating calculations. However, I don't think that it should grow into a  
full-fledged logging facility: users of the library should be let free to  
choose their preferred log library and call it in their client code. The  
tracing macros should only be used for, well, tracing calculation details  
and code flow, and in my opinion should be kept as simple as possible.
This leads to my question: is it worthwhile to have a tracing level in the  
interface? Couldn't we just dump everything (or nothing if tracing is  
disabled?)

Later,
        Luigi

----------------------------------------

Dealing with failure is easy: work hard to improve. Success is also easy to
handle: you've solved the wrong problem. Work hard to improve.
-- Alan Perlis




Reply | Threaded
Open this post in threaded view
|

Re: Tracing

Luigi Ballabio
On 02/01/05 11:52:51, Luigi Ballabio wrote:
>
> This leads to my question: is it worthwhile to have a tracing level in  
> the interface? Couldn't we just dump everything (or nothing if tracing is  
> disabled?)

Having had no answer, I assume I can go ahead and remove the tracing level  
from the interface?

Later,
        Luigi


----------------------------------------

Greenspun's Tenth Rule of Programming:
        Any sufficiently complicated C or Fortran program contains an
        ad-hoc, informally-specified bug-ridden slow implementation of
        half of Common Lisp.