Boost.Filesystem v3 as default in Boost 1.46.0?
Will the default version of Boost.Filesystem be v3 in the Boost 1.46.0 release? The current release branch still has v2 as the default (at least in <boost/filesystem.hpp>). Also, if I want to write code that works for both v2 and v3, should I test the BOOST_FILESYSTEM_VERSION macro directly? -- Jeremiah Willcock
On Tue, Jan 11, 2011 at 1:14 PM, Jeremiah Willcock <jewillco@osl.iu.edu> wrote:
Will the default version of Boost.Filesystem be v3 in the Boost 1.46.0 release? The current release branch still has v2 as the default (at least in <boost/filesystem.hpp>).
Filesystem trunk has now been merged into the release branch. Lots of server errors, but it looks like the merge did take. So for 1.46.0, V3 will be the default.
Also, if I want to write code that works for both v2 and v3, should I test the BOOST_FILESYSTEM_VERSION macro directly?
A lot of code will work with both versions. You can certainly #if on BOOST_FILESYSTEM_VERSION, but if you are having to do that often, please drop me an email with an example. I'm still open to adding compatibility hacks if they are helpful. Thanks, --Beman
Beman,
On Tue, Jan 11, 2011 at 1:14 PM, Jeremiah Willcock <jewillco@osl.iu.edu> wrote:
Will the default version of Boost.Filesystem be v3 in the Boost 1.46.0 release? The current release branch still has v2 as the default (at least in <boost/filesystem.hpp>).
Filesystem trunk has now been merged into the release branch. Lots of server errors, but it looks like the merge did take.
So for 1.46.0, V3 will be the default.
Also, if I want to write code that works for both v2 and v3, should I test the BOOST_FILESYSTEM_VERSION macro directly?
A lot of code will work with both versions. You can certainly #if on BOOST_FILESYSTEM_VERSION, but if you are having to do that often, please drop me an email with an example. I'm still open to adding compatibility hacks if they are helpful.
There is a file in Wave (boost/wave/util/filesystem_compatibility.hpp), which I needed to expand considerably to provide a compatibility layer for Boost.Filesystem V3. Please have a look and drop me a note if some of the hacks there will not be needed anymore. Regards Hartmut --------------- http://boost-spirit.com
Beman Dawes <bdawes <at> acm.org> writes:
Filesystem trunk has now been merged into the release branch. Lots of server errors, but it looks like the merge did take.
Beman, given that the trunk is being merged, please can you merge the fixes related to the incorrect streaming of filesystem paths. The issue was detailed here: https://svn.boost.org/trac/boost/ticket/4716 The patch is detailed here: https://svn.boost.org/trac/boost/changeset/64856
participants (4)
-
Beman Dawes -
Hartmut Kaiser -
Jeremiah Willcock -
Richard Hazlewood