Re: [AD] microscopic issues compiling 4.1.13 with latest MinGW packages

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


> Anyway, I could try to fix these warnings, but I'm not sure what to do
> about globals. For example, directdraw in wddraw.h. Should I change type
> to union, or just copy it to local union inside the functions generating
> warnings?

I'd rather not use unions when the problem is the cast to LPVOID*.  I'm under 
the impression that declaring a temp object of type LPVOID, passing its 
address to the function and then assigning it to the original object should 
work.  Am I mistaken?

> Also, is it ok to always name the union members "first" and "second", with 
> "first" being the original type?

Sure.

-- 
Eric Botcazou




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/