Is it a bug in qt-creator?

[J.Hilk]

hi, @Limer

I would say It's at least unusal,
4.5.1 is a rather old QtCreator version, before declaring any kind of bug, I would sugges updating to a newer/the newest version of it.

That beeing 4.8.1 and check if it's still reproduceable there.

[Limer]

@J.Hilk Yes, I have add the latest version test, but still failed.

[J.Hilk]

@Limer
well in that case I would take this to
https://bugreports.qt.io

and open a bug report.

You can post a link to the open ticket, so people can follow/have a cross reference

[jsulm]

@Limer My guess is: it is the CLang code model. You can disable that plug-in and see whether it "fixes" the issue.

[Limer]

@jsulm

no, i checked it.(disable plugin and then restart qt-creator)

[Christian Ehrlicher]

How does your LOG_INFO macro look like?

[Limer]

@Christian-Ehrlicher

#define IF_LOG_(instance, severity)     if (!plog::get<instance>() || !plog::get<instance>()->checkSeverity(severity)) {;} else

#define LOG_(instance, severity)        IF_LOG_(instance, severity) (*plog::get<instance>()) += plog::Record(severity, PLOG_GET_FUNC(), __LINE__, PLOG_GET_FILE(), PLOG_GET_THIS()).ref()

#define LOG(severity)                   LOG_(PLOG_DEFAULT_INSTANCE, severity)

#define LOG_INFO                        LOG(plog::info)

[Christian Ehrlicher]

Don't see anything obvious which could fool the parser, sorry.

[Limer]

@Christian-Ehrlicher Yes, although it hava no effect on the project building, the red underline is so uncomfortable for me ( a little obsessive-compulsive, haha... )

You can try it yourself, just need no more than 5 miuntes.

[mpergand]

I experienced the same behavior with my own macros but on linux only, not on MacOs.