Subject: [Boost-bugs] [Boost C++ Libraries] #8539: Windows Extended Path Prefix Suggestion
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-05-02 03:45:48
#8539: Windows Extended Path Prefix Suggestion
----------------------------------------------+-----------------------------
Reporter: ascend4nt@⦠| Owner: bemandawes
Type: Feature Requests | Status: new
Milestone: To Be Determined | Component: filesystem
Version: Boost 1.53.0 | Severity: Optimization
Keywords: windows filesystem extended path |
----------------------------------------------+-----------------------------
With the Windows extended path prefix:
{{{
\\?\
}}}
It might make sense if the path class pre-allocates 4 extra characters for
paths and stores the actual path at position m_pathname[4] in the string.
When a path exceeds MAX_PATH, the path functions could write the extended
path prefix at m_pathname[0] and pass that along to the Windows API. It
may make sense to return this as something like extended_path() as well.
The only problems in dealing with extended paths are that there can be no
relative path (. and ..) segments and no forward slashes.
I realize this may require alot of logic changes in the code (shifting
read/write locations); however it could cut down on additional Windows-
specific wrappers around the path class.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/8539> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:13 UTC