Re: [boost] [chrono] Interoperability with ICL and common concepts

Subject: Re: [boost] [chrono] Interoperability with ICL and common concepts
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2011-03-16 07:07:46

Joachim Faulhaber wrote:
> 2011/3/15 Stewart, Robert <Robert.Stewart_at_[hidden]>:
> > Joachim Faulhaber wrote:
>
> >> //=== in or under boost/chrono/chrono.hpp ==================
> >>
> >> namespace boost{namespace icl
> >> {
> >>     template<class Type>struct identity_element;
> >>
> >>     template<class Rep, class Period>
> >>     struct identity_element<boost::chrono::duration<Rep,Period> >
> >>     {
[snip]
> >>     };
> >> }}
> >>
> >> //==========================================================
> >
> > That looks pretty good, except perhaps instead of declaring
> > identity_element in the chrono header,
>
> hmm, this was my c++ mini satori of the day, because I realized
> authors of Boost.Chrono can avoid to do
>
> > it should
> > include <boost/icl/identity_element.hpp>
>
> just that!
>
> Recall, I wanted ICL to be Chrono agnostic and Chrono to be
> ICL agnostic.

You make a good point, but I'd expect that the Chrono specialization would be in a special header that only ICL users would include.  Thus, non-ICL Chrono users would never see the dependency.  It's not agnosticism, of course, but it is insular.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer                     using std::disclaimer;
Dev Tools & Components
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.