Warp wrote:
>   I'm afraid there are only ugly solutions to that problem. The least ugly
> of them would be to simply #include that header.

Yeah. This is supposed to support numerous underlying technologies, so 
including that header would fail when that class started using something 
other than DFB. For now, putting the "struct _IDirectFB" into the private 
part is probably better.

>   (A very ugly solution would be to use void pointers, and then reinterpret
> cast them as needed. But if you are determined to not to have to #include
> that header, then that's something that would work.)

Before that, i'd just add an extra layer of indirection to my own private 
type that was just the pile of pointers.

 > class dfbScreen::MyIDirectFB: public IDirectFB

I'm not sure what this means, but I'm pretty sure it's not going to work 
well. :-) DirectFB is all built on top of C, with fake OO stuff, so there's 
no way to get one of these for real.

Anyway, thanks for your help. I've got a satisfactory kludge. I was just 
hoping there was something less obviously kludgey I was missing.

-- 
   Darren New, San Diego CA, USA (PST)
   I ordered stamps from Zazzle that read "Place Stamp Here".

Post a reply to this message