[clazy] [Bug 367971] New Q_ENUM check also warns about Q_ENUMS for enums outside a class

[Sergio Martins via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367971

Sergio Martins  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Sergio Martins  ---
Yeah, there's no reason. clazy could give a different warning for this case but
the fix isn't trivial since the macro processor isn't connected to the AST, so
I'll just close this

-- 
You are receiving this mail because:
You are watching all bug changes.

[clazy] [Bug 367971] New Q_ENUM check also warns about Q_ENUMS for enums outside a class

[Sergio Martins via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367971

Sergio Martins  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.

[clazy] [Bug 367971] New Q_ENUM check also warns about Q_ENUMS for enums outside a class

[Sergio Martins via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367971

Sergio Martins  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |smart...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[clazy] [Bug 367971] New Q_ENUM check also warns about Q_ENUMS for enums outside a class

[Christian Ehrlicher via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367971

--- Comment #1 from Christian Ehrlicher  ---
Ok, the question is - why someone would add Q_ENUM for a enum defined in a
namespace. I currently can't see a reason for it but moc does not complain
either ... :)

-- 
You are receiving this mail because:
You are watching all bug changes.