Can TagLib2.0 require C++11 or Boost?

[Festus Hagen]

The reason I originally choose TagLib was this line from the TagLib Introduction: "No external toolkit dependencies"

Therefore I am against.

Reason is, It typically turns into a bad thing .. A can't do that because so and so won't allow it or is buggy or is slow to fix, ignores the bug fix requests, etc... etc...

I believe if you want something done right do it yourself. (or at least have the control to accomplish the goal)

Unfortunately that all means tiddly squat coming from me for I don't have the skills to do so!
I barely know what a smart pointer is let alone it's uses.

So I'm just stuck hanging on for the ride.

As for compilers, I use various flavors of MinGW and C++11 support is still pretty shaky, especially on Windows.

-Enjoy
fh : )_~




----- Original Message -----
From: Tsuda Kageyu <tsuda.kageyu at gmail.com>
To: "taglib-devel at kde.org" <taglib-devel at kde.org>
Cc: 
Sent: Sunday, November 17, 2013 6:20 PM
Subject: Can TagLib2.0 require C++11 or Boost?


Hi guys.

I'm thinking about making changes that requires at least one of C++11 or 
Boost Smart Pointers to TagLib 2.0. 

Currently, TagLib2 has self-implemented smart pointers when neither 
std::shared_ptr nor boost::shared_ptr is available. I will remove it to 
make TagLib more robust (and hopefully more efficient) by leaving all 
the atomic operations for reference counting to the standard library or 
Boost, but it also means to abandon some old compilers that Boost 
doesn't support.

So I'd like to ask you what kind of compilers are you using to build 
TagLib. Is somebody using the compilers which are not supported by 
Boost?

This change only affects the users who builds TagLib themselves. It 
doesn't affect the people who uses TagLib as a package.

Kageyu.
_______________________________________________
taglib-devel mailing list
taglib-devel at kde.org
https://mail.kde.org/mailman/listinfo/taglib-devel