TagLibAmalgam: A new way to use TagLib

Manfred Schwind lists at mani.de
Thu Apr 19 13:31:02 UTC 2012

> Fixing the warnings means submitting a pull request for a change to
> the official taglib repository

Maybe I should try that. ;-)

> you can't fix a warning in the amalgamation

True, of course. That's what I said.

> A non virtual destructor could in theory be a problem, if a derived
> class is deleted through an alias to its base. Does this happen in
> practice? I rather doubt it.

"Delete called on 'const TagLib::FileRef::FileTypeResolver' that is abstract"
sounds like that's the case here. An abstract class can't be instantiated, so the "real" class of the deleted instance must be some derived class.


More information about the taglib-devel mailing list