[MPlayer-dev-eng] Re: Another warning and functionality fix

[Daniel Egger]

Hija,

> this is probably not the correct fix. using another pointer type where
> void is expected should not alone generate a warning.

You're right.

> (volatile), and it might be a good idea to look at why they do and 
> whether they need it... at a glance, i see no reason why these
> should be volatile; it looks like it would just slow things down a
> good bit. maybe to work around a bug in a broken compiler version??

I haven't noticed the volatile on first inspection but you're absolutely
that it doesn't belong there and also is superfluous in most other
places. I'll be testing some other changes a bit more and will report
back with a cleanup if it's really unneeded. 

-- 
Servus,
       Daniel