Re: gcc 4.2 generates error that was OK before
Re: gcc 4.2 generates error that was OK before
- Subject: Re: gcc 4.2 generates error that was OK before
- From: Alastair Houghton <email@hidden>
- Date: Tue, 22 Sep 2009 21:26:56 +0100
On 22 Sep 2009, at 21:17, Steve Mills wrote:
On the Mac, those are both typedef'd to void. On Windows, they're
typedef'd to int and size_t. Maybe it's just the "static" that's
making it puke? No, getting rid of that didn't help. Still, I don't
see the need for it in the *declaration* of hsGGlyphCacheHandler.
Changing the 2 typedefs below to #defines made it work.
I wonder if sticking "typename" in explicitly to tell the compiler
that you're talking about types helps? Something like:
#ifndef __cplusplus
#define typename
#endif
static typename hsNewHandler_ReturnType hsGGlyphCacheHandler
(typename hsNewHandler_ParamType);
I'm not sure it's *supposed* to be necessary in this context, but I'm
equally not sure it isn't and as I don't have the standard handy all I
can suggest is that you try it and see.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden