Dmitry Arkhipov

> > Using the host's value seems like a reasonable default. > > It's not. Consider `b2 toolset=X,Y` where X is 32 bit and Y is 64 bit. ``` #...

I might have a solution: add value `native` , which will be the default.

People would be able to do ``` using openssl : : "C:/vcpkg/installed/x64-windows/include" "C:/vcpkg/installed/x64-windows/lib" : native ; using openssl : : "C:/vcpkg/installed/x64-windows/include" "C:/vcpkg/installed/x64-windows/lib" : 64 ; using openssl : : "C:/vcpkg/installed/x86-windows/include"...

Also, consider this. I am currently having in my user-config.jam ``` using gcc : 12 : i686-w64-mingw32-g++-posix : : windows 32 pthread ; using gcc : 12 : x86_64-w64-mingw32-g++-posix :...

@grafikrobot can you comment on this PR?

I will first answer design/UI questions. > Why doesn't this integrate with the existing package support. I.e. this seems to behave entirely different than existing package support. Why? This _does_...

@grafikrobot can we return to discussing this PR?

``` import print ; make a.txt : : @write ; rule write ( target : srcs * : props : ) { print.output $(target) ; print.text "line1" "line2" : overwrite...

My snippet had a typo (a didn't test it when I posted it). The correct jam script that creates a `project-config.jam` in current directory is ``` make project-config.jam : :...

Template parameter names imply that this algorithm operates on a range of output iterators. But there's no such thing. Output iterators aren't required to have equality comparison. The algorithm actually...