Silence ushort ambiguity errors

[FestusHagen]

No description provided.

[TsudaKageyu]

Thank you for your catch and fix @FestusHagen.

[TsudaKageyu]

Honestly, I'd like to remove such typedefs and use standard integer types in taglib2 branch.

[sbooth]

I agree with that! Anything we can do to avoid unnecessary duplication is
worthwhile.

On Mon, Nov 30, 2015 at 10:47 AM Tsuda Kageyu notifications@github.com
wrote:

Honestly, I'd like to remove such typedefs and use standard integer types
in taglib2 branch.

—
Reply to this email directly or view it on GitHub
#691 (comment).

[FestusHagen]

I'd like to see it consistent ...

-Enjoy

[TsudaKageyu]

It looks like the types like ushort are defined in some standard header.
Assuming that, the ambiguity errors may occur in any header. I think we'd better add TagLib:: to all such types in the public headers.

[TsudaKageyu]

Well, I will create another issue to discuss it.

[TsudaKageyu]

I have eliminated all the custom integer types from the source. I hope this kind of issues will never happen again.