From: Arjen M. <arj...@wl...> - 2006-08-21 04:30:54
|
> Hi all, > > I tested the driver Andrew sent to me personally, and I just checked, > that the new driver is also in cvs now. I think Arjen tested the old > driver, not the new one, since this driver works for me on Visual C++ > without problems (apart from the maximizing bug). > I updated my installation before trying this out, but that may have been too early :). I will try again asap. > The new Debug macro is obviously buggy? If I change line 150-154 to > > #define Verbose(...) do {if > (pls->verbose){fprintf(stderr,__VA_ARGS__);}}while(0) > #define Debug(...) do {if > (pls->debug){fprintf(stderr,__VA_ARGS__);}}while(0) > > /* #define Debug(a) do {if (pls->debug){fprintf(stderr,(a));}}while(0) > */ > > then it compiles again and works the same as in visual c++ build. So I > think Arjen just needs to try it again after a cvs checkout. > > Andrew, could you please have a look in this debug macro issue (line > 150-154)? > > The macro definition with the ellipsis caused problems under MSVC/C++ 6.0 - it does not like them. That is why I changed the macro. A very brief inspection seemed to show calls with only one argument. Hence the change. (MSVC/C++ 6.0 does _not_ complain about the two calls I found just now with more than one argument. Odd.) Regards, Arjen |