On Mon, Feb 22, 2021 at 3:10 PM Richard Hodges via Boost < boost@lists.boost.org> wrote:
On Mon, 22 Feb 2021 at 14:46, Niall Douglas via Boost < boost@lists.boost.org> wrote:
The very first item in the Examples part of the docs is dynamically wiring together components using a runtime-supplied XML file.
Yes proposed Boost.DI is compile time, but it can also do runtime. I agree that the docs don't make this as obvious as they could.
Comprehensive documentation around the runtime I use case might make it compelling for me.
Especially if the assembled components are across shared-libraries. For true Java-like runtime wiring of components picked up from the classpath. Imagine a core no-dependency statically linked exe, with embedded SQLite backend, and simple built-in logger. Useful on its own, can be shared / open sourced. But which can be configured at runtime via CLI or file configs, to use a more sofisticated Logstash logger, a different backend, a different WebSocket impl, etc... With those parts closed sourced, and for a fee. Like a freemium model. --DD