Boost logo

Geometry :

Subject: Re: [geometry] io - WKB
From: Barend Gehrels (barend_at_[hidden])
Date: 2013-07-22 14:05:21

On 22-7-2013 0:46, Mateusz Loskot wrote:
> On 21 July 2013 22:23, Bruno Lalande <bruno.lalande_at_[hidden]> wrote:
>> I don't think a container is a good choice. Streams were invented for a
>> reason (regardless of the language), which is to allow tranfers of data
>> without loading it all in memory. If a user wants to load directly from/to a
>> file, a network or any out-of-memory resource, he needs streams in order to
>> minimize memory consumption. If however he wants it all in a container for
>> any reason, stream iterators are here for that.
> Bruno,
> I agree.
> I answered a general question as it was asked without any details
> regarding where it is aimed to be used.
> On the other hand, I followed read_wkt which takes container.
> I guess it could be changed to streams.

Yes, the WKT input might can be changed to streams. I will think about
that. Internally it uses Boost.Tokenizer. It takes a string as input.

To be clear: wkt-output uses streams already (from the beginning). It is
a stream-manipulator.

WKB input is already based on stream iterators (though random access),
contrary to WKT.
What is your reason to re-implement WKB using Boost.Spirit V3?

Regards, Barend

Geometry list run by mateusz at