Hi, After complaints about the customization way, I'm making Boost.Range support for ATL/WTL/MFC collections and strings. I know current Boost.Range contains a few and those are somewhat illegal. ;-) Well, before I upload them to Vault, I want a namespace and macro-prefix for the implementation something like boost::ranges::??? and BOOST_RANGES_???. Where can I place them? -- Regards, Shunsuke Sogame
Shunsuke Sogame wrote:
Hi,
After complaints about the customization way, I'm making Boost.Range support for ATL/WTL/MFC collections and strings. I know current Boost.Range contains a few and those are somewhat illegal. ;-)
ok, I never got to test them properly.
Well, before I upload them to Vault, I want a namespace and macro-prefix for the implementation something like boost::ranges::??? and BOOST_RANGES_???. Where can I place them?
did you make "ordinary" support the hard way or did you go for the easier make_mfc_range()? Either way, I think the boost namespace is ok. -Thorsten
Thorsten Ottosen wrote:
Well, before I upload them to Vault, I want a namespace and macro-prefix for the implementation something like boost::ranges::??? and BOOST_RANGES_???. Where can I place them?
did you make "ordinary" support the hard way or did you go for the easier make_mfc_range()?
Either way, I think the boost namespace is ok.
Ordinary support, of course! That's life. I plan to use 'boost::range_detail::msvc'. -- Regards, Shunsuke Sogame
Shunsuke Sogame <mb2act@yahoo.co.jp> writes:
Thorsten Ottosen wrote:
Well, before I upload them to Vault, I want a namespace and macro-prefix for the implementation something like boost::ranges::??? and BOOST_RANGES_???. Where can I place them?
did you make "ordinary" support the hard way or did you go for the easier make_mfc_range()?
Either way, I think the boost namespace is ok.
Ordinary support, of course! That's life. I plan to use 'boost::range_detail::msvc'.
That doesn't seem right; other compilers can build ATL/WTL/MFC code. -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams wrote:
Shunsuke Sogame <mb2act@yahoo.co.jp> writes:
Thorsten Ottosen wrote:
Well, before I upload them to Vault, I want a namespace and macro-prefix for the implementation something like boost::ranges::??? and BOOST_RANGES_???. Where can I place them?
did you make "ordinary" support the hard way or did you go for the easier make_mfc_range()?
Either way, I think the boost namespace is ok.
Ordinary support, of course! That's life. I plan to use 'boost::range_detail::msvc'.
That doesn't seem right; other compilers can build ATL/WTL/MFC code.
The implementation is shared for ATL, WTL and MFC. Will 'boost::range_detail::microsoft' be right? (though users never see) -- Regards, Shunsuke Sogame
participants (3)
-
David Abrahams -
Shunsuke Sogame -
Thorsten Ottosen