Summary: | Expose tag stripping in the taglib C interface | ||
---|---|---|---|
Product: | [Frameworks and Libraries] taglib | Reporter: | Linus Walleij <triad> |
Component: | general | Assignee: | Scott Wheeler <wheeler> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Exposes ID3v2 tag stripping in the C API |
Description
Linus Walleij
2007-09-18 23:23:42 UTC
Created attachment 21653 [details] Exposes ID3v2 tag stripping in the C API Patch from mail http://mail.kde.org/pipermail/taglib-devel/2007-September/000728.html To be honest, I don't really consider this a core functionality enough to include it in the C interface, which is more or less a mirror of TagLib::Tag. OK, it's sad because any C app that wants to do this simple operation will have to include a secondary ID3 parser for this single purpose, but I already wrote that code so I can live with it. Well ... or they'll have to write a few lines of C++. But that's always the problem when designing interfaces, whether graphical or API. The just-one-more-thing approach tends to lead to a mess, even if any particular one thing doesn't. Yeah I get the point :-) I'll give up and write a custom interface wrapper in C++, it's no big deal. |