> MSVC 6 SP3 definitely does NOT like varargs macros.
>
> ;^(
>
> I tried about as many combinations as I could think of, no go.
Okay, I'll change them to straight function calls.
> Sorry.
Hey, it ain't your fault :)
-- Gareth
___
Mesa-dev mailli
>Here's what they kinda look like now (from memory):
MSVC 6 SP3 definitely does NOT like varargs macros.
;^(
I tried about as many combinations as I could think of, no go.
Sorry.
___
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.or
> I don't know how your macros are implemented, but variable length
> may not be at all supported on MSVC variants, in fact it may not
> even treat it as a warning but treat it as a compile-time error.
Here's what they kinda look like now (from memory):
#ifdef DEBUG
#ifdef _WIN32
#define DEBU
Gareth,
I don't know how your macros are implemented, but variable length may not be at
all supported on MSVC variants, in fact it may not even treat it as a warning
but treat it as a compile-time error. ;^(
Is your var-arg macros in VSS that I can check them out?
-Ted
__
> Is the logging code only enabled when building in debug mode? I'd
> say the warnings are OK then. But when the end user builds with
> optimizations I'd rather not see a bunch of warnings.
Yes, the logging code is only built in debug mode. I'll have to see if the
compiler still complains abou
Hughes, Gareth wrote:
>
> I've spent a lot of time over the last week or two working on the
> self-intersecting contour thing, and decided to finally update my debugging
> output to make it a little easier to use. I've done the GLX thing and made
> the debug level configurable via an environment
I've spent a lot of time over the last week or two working on the
self-intersecting contour thing, and decided to finally update my debugging
output to make it a little easier to use. I've done the GLX thing and made
the debug level configurable via an environment variable. To do this, I
changed
