How about a TRACE macro that compiles out in release builds? I have
a decent debugging framework for Windows that I could check in. I don't
know what the Linux equivalent is to the Win32 OutputDebugString().
c
On Fri, 17 Mar 2000, Mayhem & Chaos Coordinator wrote:
> > Hi. Is there any documentation on the debug functionality? I looked in
> > player.cpp for relevant command-line options (none), and in debug.h
> > and debug.cpp. How do I turn it on?
>
> Not really -- the function Debug_v() is a function that I use as a
> replacement to printf(). This is my primary debugging tool and it requires a
> small executable to display the output. However, I usually remove my
> debugging statements before checking in code to CVS, so there is nothing to
> turn on.
>
> We also have a logging facility, but we haven't really put many logging
> statements into the code yet. The decode pipeline uses them, but not very
> extensively either.
>
> > BTW, I would like to maintain a development FAQ (because I ask so
> > many questions?). Does such a thing exist, or should I just go
> > ahead and start compiling it?
>
> Go for it...
>
> --ruaok Freezerburn! All else is only icing. -- Soul Coughing
>
> Robert Kaye -- [EMAIL PROTECTED] http://moon.eorbit.net/~robert
>
> _______________________________________________
> [EMAIL PROTECTED]
> http://www.freeamp.org/mailman/listinfo/freeamp-dev
>
----------------------------------------------------
| Chad Loder - Somerville, MA, USA |
| EMail: [EMAIL PROTECTED] |
| Home Page: http://www.ccs.neu.edu/home/cloder |
----------------------------------------------------
_______________________________________________
[EMAIL PROTECTED]
http://www.freeamp.org/mailman/listinfo/freeamp-dev
