Geometry Boost List: Re: [geometry] Default model for Ring Concept should *be* Container, not inherit from it

Subject: Re: [geometry] Default model for Ring Concept should *be* Container, not inherit from it
From: Volker Schöch (vschoech_at_[hidden])
Date: 2012-02-16 09:18:55

Barend,

> What is exactly the requirement for multi-polygon that is the problem? 
> Sorry if I missed that point earlier somewhere. A MultiPolygon (the 
> concept) should behave as a range, that is basically all. Our 
> multi_polygon derives from a std::vector, but that is not necessarily 
> the case - you can also contain it and adapt it to Boost.Range.

I see. You may call me lazy b/c I simply modeled it after your example and didn't bother implementing the Boost.Range interface. It's good to know that I could do it if I absolutely wanted to.

Thanks for taking your time,
   Volker

--
Volker Schöch | vschoech_at_[hidden]
Senior Software Engineer
think-cell Software GmbH | Chausseestr. 8/E | 10115 Berlin | Germany
http://www.think-cell.com | phone [phone] | US phone [phone]
Amtsgericht Berlin-Charlottenburg, HRB 85229 | European Union VAT Id DE813474306
Directors: Dr. Markus Hannebauer, Dr. Arno Schoedl