> Prior to the load.
> That means you need to require your OS to provide a way to get that string for
a potential plugin before it is loaded.
Does it have to be prior to the load? What’s wrong with loading it as long as you don’t use stdlib constructs across ABI boundary until after verifying some match?
Jeremy
On Thursday 7 November 2024 07:29:38 Pacific Standard Time Jeremy Rifkin via
Std-Proposals wrote:
> My suggestion: Rrquire plugins to publish a C string with some identifier
> indicating the standard library being used (e.g. "libstdc++" or "libcxx"
> depending on preprocessor macros set by the libraries). Then check that on
> load.
Prior to the load.
That means you need to require your OS to provide a way to get that string for
a potential plugin before it is loaded.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Principal Engineer - Intel DCAI Platform & System Engineering
--
Std-Proposals mailing list
Std-Proposals@lists.isocpp.org
https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals