23 Mar
2013
23 Mar
'13
4:41 p.m.
On Sat, Mar 23, 2013 at 2:01 PM, Alexander Lamaison
[...] Is it time for a Boost.Filesystem v4 to result from an in-depth discussion on here? I'd hope it would take the best of v3 while removing some of the hurt it introduced in the process. For example, my top two issues are: - unclear generic/native path handling - methods returning a 'path' for stuff that isn't a path but just needs a unicode string
Perhaps people can reply to this thread with any gripes they have?
See a related thread of things that boost.filesystem got wrong: http://boost.2283326.n4.nabble.com/boost-filesystem-path-frustration-td46417... -- Yakov