RE: Hdot264-devel digest, Vol 1 #46 - 2 msgs

Greetings all,
     I've been following this list since I first
posted a while back.  Since, I don't know much about
the algorithms used in video, I am going to tag along
on this group as the project developes until I
understand how the thing works.  Then I would like to
pitch in any way that I can.

--Gopal--
"2. Regarding debugging we cannot go for #define DEBUG
sort of things.  We can save a lot of time in
compilation if have a command line switch itself. we
can have wrapper functions which will print out
necessary information as dictated by cmd line args."
--Gopal--

On this issue, it is better to use the #define DEBUG
in the following manner.

#define DEBUG	

main()
{
	:
	:
#ifdef DEBUG
	printf("Variable total is %d\n",total);
#endif
	:
	:
}

This way, the #ifdef statement is evaluated at compile
time.  A normal "if" statement, "if (debug) printf
()", would be evaluated at run time.  Even if we are
not debugging at the moment, the "if" statement is
still evaluated.  When we are using C and asm to
squeeze every nanosecond out of this thing, it only
makes sense to use the compiler's #define statement.

--AITOR--
    http://bs.hhi.de/~wiegand/publications.html
--AITOR--

Thanks AITOR for the link.  This looks like a gold
mine for this project.  After reading all of these, I
should be up and running with y'all in no time.

Cheers,

Phillip S. Givens

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1