String::detach() not thread-safe?

[Tsuda Kageyu]

Hmm, I was wrong. PR #493 won't fix your problem, PR #493 will fix only
ByteVector...

2015-05-09 23:30 GMT+09:00 Tsuda Kageyu <tsuda.kageyu at gmail.com>:

> Hi Kevin,
>
> I made another PR #493 that will fix your problem as well. But it hasn't
> been reviewed yet.
>
> Cheers,
> Kageyu
>
> 2015-05-09 22:05 GMT+09:00 Kevin André <hyperquantum at gmail.com>:
>
>> Hi,
>>
>> On Sat, Nov 15, 2014 at 2:03 PM, Tsuda Kageyu <tsuda.kageyu at gmail.com>
>> wrote:
>> > I suggested a pull request that will fix it:
>> > https://github.com/taglib/taglib/pull/433
>>
>> It seems the merge request was denied because the changes were
>> considered too complicated. So I need another solution.
>>
>> I think only the static members need to be fixed. Like String::null.
>> Either the static members need to be made thread-safe, or they will
>> need to be removed.
>> Or I will need to create a taglib worker thread in my application,
>> with a queue to handle all tasks that need taglib. That would
>> complicate things a lot, I guess.
>>
>>
>> Regards,
>>
>> Kevin
>> _______________________________________________
>> taglib-devel mailing list
>> taglib-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/taglib-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/taglib-devel/attachments/20150514/dfa4921c/attachment.html>