[XviD-devel] Did OutputDebugStringf(const char*, ...) get lost in the Forbidden Forest?

Kerewin pyromedia at tiscali.co.uk
Wed Feb 15 11:36:05 CET 2006


Hi,

Explaining -0.0 in benchmark, I think.

#include <stdio.h>
#include "debug.h"

int main(int argc, char* argv[])
{
	OutputDebugStringf("One:%d Two:%f 19:%x\n", 1, -0.0000000002f, 19);
	getchar();
	return 0;
}

One:1 Two:-0.000000 Nineteen:13

The scanner is determining the sign of the parameter rather than the
adjusted parameter... I guess Scientific Notation is called for in the
benchmarking output as reams of 0.0s or -0.0s aren't very interesting.

Kerewin.


-----Original Message-----
From: xvid-devel-bounces at xvid.org [mailto:xvid-devel-bounces at xvid.org] On
Behalf Of pete
Sent: 15 February 2006 09:22
To: xvid-devel at xvid.org
Subject: Re: [XviD-devel] Did OutputDebugStringf(const char*,...) get lost
in the Forbidden Forest?

hi there,

On Wed, 15 Feb 2006 03:46:15 -0000 "Kerewin" <pyromedia at tiscali.co.uk>
wrote:
> I am orf to roll an OutputDebugStringf(lpcstr c,...) coz release 1.1.0
lacks
> debug.c. The I am going to have -0.0 cups of coffee.

debug.c (including OutputDebugStringf) is available within the cvs
repository.

cheers,
-- pete

_______________________________________________
XviD-devel mailing list
XviD-devel at xvid.org
http://list.xvid.org/mailman/listinfo/xvid-devel



More information about the XviD-devel mailing list