I dont understand why this patch fixes anything, this is a noop ?
- TRACE("(%p)\n",ds3db);
/* volume, at which the sound will be played after all calcs. */ D3DVALUE lVolume = 0; @@ -205,6 +204,7 @@ D3DVALUE flFreq, flBufferVel, flListenerVel; #endif
+ TRACE("(%p)\n",ds3db);
===== Sylvain Petreolle (spetreolle at users dot sourceforge dot net) ICQ #170597259 No more War !
"What if tomorrow the War could be over ?" Morpheus, in "Reloaded".
For the Law of Oil and Fire, Im an European that lives in France. For all my Brothers and friends, Im a human living on Earth.
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
On Thu, 22 May 2003, Sylvain Petreolle wrote:
I dont understand why this patch fixes anything, this is a noop ?
No, in (old?) C rules you can't have variable declarations after statements. The TRACE is a statement.
On Thu, May 22, 2003 at 07:38:27PM +0200, Sylvain Petreolle wrote:
I dont understand why this patch fixes anything, this is a noop ?
TRACE("(%p)\n",ds3db);
/* volume, at which the sound will be played after all calcs. */ D3DVALUE lVolume = 0;
@@ -205,6 +204,7 @@ D3DVALUE flFreq, flBufferVel, flListenerVel; #endif
- TRACE("(%p)\n",ds3db);
Well, us old-timers using no-C99 compilers need to have the variables defined before any instructions...
So without the patch, compilation bombs, with the patch it compiles :-)
Lionel
PS: actually, it's my fault, when I told Robert that his patch was working, I forgot to tell him that I had an error compiling it on my GCC 2.95.3 set-up...