[OpenMethod] Boost.OpenMethod review scheduled

The review for the proposed Boost.OpenMethod library by Jean-Louis Leroy is scheduled to take place from April 28 to May 07. OpenMethods solve the Expression Problem by making it possible to define free virtual functions, i.e. virtual functions that exist outside of a class The library repository is here: https://github.com/jll63/Boost.OpenMethod. The documentation is here: https://jll63.github.io/Boost.OpenMethod.

On Fri, Apr 11, 2025 at 6:25 AM Дмитрий Архипов via Boost < boost@lists.boost.org> wrote:
The review for the proposed Boost.OpenMethod library by Jean-Louis Leroy is scheduled to take place from April 28 to May 07.
OpenMethods solve the Expression Problem by making it possible to define free virtual functions, i.e. virtual functions that exist outside of a class
The library repository is here: https://github.com/jll63/Boost.OpenMethod. The documentation is here: https://jll63.github.io/Boost.OpenMethod.
Piggybacking on this, I'd like to take this opportunity to demo a new workflow for Boost review! I'm hoping some brave souls will help me out and attempt this. It's a vcpkg registry full of Boost and libraries under review: https://github.com/cmazakas/vcpkg-registry-test The repo even comes with an OpenMethod demo as well. Hopefully this'll make it a bit easier for people to try out the library without interrupting their workflows. The library (OpenMethod) should automatically download along with all of the required dependencies and is non-intrusive to existing boost roots we may all be developing against. If you're unfamiliar with vcpkg, the docs for it can be found here: https://learn.microsoft.com/en-us/vcpkg/ But a basic setup of the tool will basically be: git clone https://github.com/microsoft/vcpkg.git cd vcpkg ./bootstrap-vcpkg.sh
From there, you'll find the cmake toolchain file located in `vcpkg/scripts/buildsystems/vcpkg.cmake`
This toolchain file is what basically drives the entire UX for vcpkg. The repo (vcpkg-registry-test) should have instructions if you're still unclear. For people with existing installs of vcpkg, make sure you do a `git pull` to get the latest commits of vcpkg because this is what helps power the registry and the required vcpkg-configuration.json. - Christian

Piggybacking on this, I'd like to take this opportunity to demo a new workflow for Boost review!
Thanks for this! I just tried it. My vcpkg repository was quite behind and cmake complained about a missing tools.xml or something like that. After re-boostrapping the error went away and it all built without a hiccup. I'll send you a PR to add a method call to the example. Also I'll generate the CMakeList.txt with boostdep, so we can get rid of the patch. J-L

On Fri, Apr 11, 2025 at 10:41 AM Jean-Louis Leroy via Boost < boost@lists.boost.org> wrote:
Piggybacking on this, I'd like to take this opportunity to demo a new workflow for Boost review!
Thanks for this!
I just tried it. My vcpkg repository was quite behind and cmake complained about a missing tools.xml or something like that. After re-boostrapping the error went away and it all built without a hiccup.
I'll send you a PR to add a method call to the example. Also I'll generate the CMakeList.txt with boostdep, so we can get rid of the patch.
J-L
Alright, updated the demo! Now it looks very spiffy. Let me know if there's anything else. I still encourage everyone to pull down and try out the new workflow. - Christian
participants (3)
-
Christian Mazakas
-
Jean-Louis Leroy
-
Дмитрий Архипов