If at all then not in moc but rather in QMetaObject::normalizedSignature(). But in general this should work, maybe the problem is somewhere else?
If it's known - that I do not know but you can check that yourself using the task-tracker.
If at all then not in moc but rather in QMetaObject::normalizedSignature(). But in general this should work, maybe the problem is somewhere else?
If it's known - that I do not know but you can check that yourself using the task-tracker.
Yep.
It should work but it doesn't work. We have two identical (from C++ pov) signatures and one is treated differently by moc than the other. Isn't this clearly a bug?
What do you mean by maybe the problem is somewhere else?
There were a couple of tickets about moc and signatures, all fixed.
I created a ticket for this.
The documentation gives an example almost identical to yours (it uses a pointer and not a reference), so I assume they checked that it works. You might check if changing the reference to a pointer makes it work.
In some other part of the code or because of some non-printable character. I'm just guessing, it's simply hard to believe the example from the docs doesn't work.What do you mean by maybe the problem is somewhere else?
But moc has nothing to do with this...There were a couple of tickets about moc and signatures, all fixed.
What I presented in my op is not the example from the docs but my code. I only copied and pasted signal declaration directly from the docs to show it's part of qt and not mine.
In the most narrow sense moc is only a compiler but in a broader sense it's name of whole concept, system (name it as you like) which this compiler is only one part of. When using moc in the second sense QMetaObject::normalizedSignature() is vital part of moc.
On the other hand, if we agree moc is only a compiler than how should we call the whole system of meta information in qt?
Bookmarks