|
Boost : |
From: Cameron Angus (cjangus_at_[hidden])
Date: 2024-12-19 12:06:27
> Wouldn't you need to still ifdef-out your includes?
Yes. While it seems like it would be nice for 'export' to be ignorable, I
don't really see that it would make much of a difference to how easily a
library can be modularized. Especially given that we have export blocks, so
it's not necessary to put a macro in front of every individual declaration
anyway.
On Thu, 19 Dec 2024 at 20:36, Ruben Perez via Boost <boost_at_[hidden]>
wrote:
> On Tue, 17 Dec 2024 at 16:30, Peter Dimov via Boost
> <boost_at_[hidden]> wrote:
> >
> > Chuanqi Xu wrote:
> > > For authors of libraries, after boost introduce modules, you only
> need to do 2
> > > extra things:
> > > - In headers, add a macro (assume its name as BOOST_MODULE_EXPORT,
> > > which will be âexportâ conditionally) to the entities that need to be
> exported.
> >
> > Would have been nice if the `export` keyword was accepted and silently
> ignored
> > when outside of module.
>
> Wouldn't you need to still ifdef-out your includes?
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk