Jim King
Jim King
The CI builds on AppVeyor pass, but they use the following build command (it is mingw inside msys2): ``./b2 libs/iostreams toolset=gcc-mingw32 cxxstd=03 address-model=32 variant=release,debug -j3`` I was going to suggest...
Look at the AppVeyor CI builds where MSVC 14.0 (2015) is tested: https://ci.appveyor.com/project/eldiener/iostreams/builds/22626745 I only see: ``` c:\projects\boost-root\boost\test\impl\execution_monitor.ipp(1296) : warning C4702: unreachable code ``` Look at the regression test matrix...
Well, he wrote the test... :)
Look at https://github.com/boostorg/iostreams/blob/develop/src/mapped_file.cpp#L267 - the code in iostreams is calling ::open directly, so if the path is wide coming into the code here, there's no way for it to succeed.
Yes, it looks like the documentation is incorrect here.
I think the proper solution here is likely the following on lines 129, 130: ``` else if(way != ::std::ios_base::cur || (which & ::std::ios_base::in) ) // (altering in&out is only supported...
@PHackett any thoughts on this approach?
Could you be more specific, perhaps provide an example use?
@jaykrell CI is working again, if you rebase it'll run everything now.
@jaykrell CI is working again, if you rebase it'll run everything now.