Re: [AD] trying to make allegro compatible with MFC

["Eric Botcazou" <ebotcazou@xxxxxxxxxx>]

> for me it is ok

It looks like the two preprocessors don't behave the same.
Is there any specialist of preprocessors here ?

What's the "standard" behavior (if any) for the following lines ?

struct RGB { ... };

#define RGB(r,g,b)  f(r,g,b)
#define WINDOWS_RGB RGB
#undef RGB

int foo(void)
{
   return WINDOWS_RGB(255, 0, 255);
}

Javier, could you post the definition of the Win32 RGB macro from the
Platform SDK ?
I'd rather use it than the MinGW32 version.

> yes, but that is purpose, since in any way windows.h is just C code (and
> the afxwin.h header cannot be inside the extern "C" for obvious reasons)

Huh... isn't extern "C" precisely intended for wrapping C code ?

> you can make windows.h inside extern "C" if you want though, just making
> sure you dont include afxwin.h inside this scope

Of course.

-Eric