[Development] On the use of the inline keyword

[Thiago Macieira]

On Thursday, 24 August 2023 05:37:28 PDT Volker Hilsheimer via Development 
wrote:
> Before we now go on a campaign to clean all this up (as is already being
> reviewed for qstring.h), I’d rather evaluate other options for the existing
> code base.
> 
> Can we disable this warning some in some other way on MinGW? Or, knowing the
> likely reason for it, live with it and fix things when and if we run into
> them (which seems to be reasonably rare)?

First of all, this only applies to exported classes. Classes without the 
export macro do not need this. Your regexp might have found too many hits.

I don't know if GCC/MinGW is printing that warning for a good reason or not. 
In the past, I think it led to compilation errors that a function that needed 
to be imported wasn't. But I can't think of a good reason why that would be, 
because if it's inline, it isn't imported or exported.

That warning looks like a bug in the compiler instead. So if there's no ill-
effect, I'd just disable and ignore it.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5152 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20230824/f5b3aa5a/attachment.bin>