Re: [boost] [Modularization] A new approach to header modularization

Subject: Re: [boost] [Modularization] A new approach to header modularization
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-05-29 07:53:30

JOAQUIN M. LOPEZ MUÑOZ wrote
On Thursday, May 28, 2009 5:18 PM
> ________________________________________
> De: boost-bounces_at_[hidden]
> [boost-bounces_at_[hidden]] En nombre de Beman Dawes
> [bdawes_at_[hidden]]
> Enviado el: jueves, 28 de mayo de 2009 23:06
> Para: boost_at_[hidden]
> Asunto: Re: [boost] [Modularization] A new approach to header
>   modularization
> >
> > As boost grows, filling the boost/ with headers becomes
> > less and less attractive.
>
> I don't see why this is less attractive than having boost/ filled with
> folders.

Because it doubles the number of entries per library: filesystem.hpp and filesystem.

> > Of course we have to leave the current headers there for
> > compatibiltiy, but that location could be deprecated and eventually
> > only <boost/filesystem/filesystem.hpp> supported.
>
> *This* is less attractive to me; I think a Boost lib is
> entitled to have at least one top level header; many use
> it to include all or the the most usual components.

There's no entitlement involved.  Leaving such files in the root directory dissociates them from the rest of the library which mitigates against modularization, which is a laudable goal.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.