Re: poke-1.0 and GCC < 4.6

[Bruno Haible]

Hi José,

> I am not a big fan on the cpp solution, but since I can't think on a
> better one, lets put it in for now.

I looked into these in more detail.

In one case, the duplicate typedef is simply redundant.

In two cases, the best approach I can see is a separate .h file.

In two cases, a separate .h file is overkill, and it is simpler to just
write 'struct foo *' in place of 'foo' in one or two places. If the typedef
would change in the future, GCC would emit a warning.

How about this? Tested on the said machine with GCC 4.1.x.

0001-Fix-a-compilation-error-with-GCC-4.6.patch
Description: Text Data

0002-Fix-a-compilation-error-with-GCC-4.6.patch
Description: Text Data

0003-Fix-a-compilation-error-with-GCC-4.6.patch
Description: Text Data

0004-Fix-a-compilation-error-with-GCC-4.6.patch
Description: Text Data

0005-Fix-a-compilation-error-with-GCC-4.6.patch
Description: Text Data