[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: poke-1.0 and GCC < 4.6

From: Bruno Haible
Subject: Re: poke-1.0 and GCC < 4.6
Date: Tue, 02 Mar 2021 02:43:07 +0100
User-agent: KMail/5.1.3 (Linux/4.4.0-203-generic; KDE/5.18.0; x86_64; ; )

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.

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

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

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

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

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]