Subject: Re: [geometry] Adaption of legcay hierarchy to Boost.Geometry model
From: Barend Gehrels (barend_at_[hidden])
Date: 2013-02-09 07:38:35
On 8-2-2013 8:57, ???? ??????? wrote:
> OK, it seems that I have found answer for this question.
> In/linestring_concept.hpp/. it's mentioned that besides
> specialization of traits::tag and and lifting of Boost.Range Random
> Access concepts custom linestring class
> also must "implement std::back_insert_iterator either by implementing
> push_back or by specializing
> std::back_insert_iterator". The same if for the Ring Concept. I really
> can't understand how to "specialize
> std::back_insert_iterator" but it seems to me that this phrase means
> the necessity of specialization of
> structs *resize*, *push_back* and *clear* from /mutable_range.hpp/,
> which are used by *append* and *assign* algorithms.
> I have not tested this solution yet but it seems to be right taking in
> account that Boost.Polygon data structures
> are adapted to Ring and Polygon Concepts in the same way.
Sorry for my late answer on this. Indeed the "mutable range" should be
used / specialized for these operations. So the linestring itself can
stay as it is.
In another mail you referred to the solution about legacy classes, that
was in cooperation with Mats who did the basics this adaption, I
contributed only small tests and additions there.
Geometry list run by mateusz at loskot.net