Boost logo

Geometry :

Subject: [geometry] WKB support (write)
From: Mats Taraldsvik (mats.taraldsvik_at_[hidden])
Date: 2013-11-29 17:00:15


I might need WKB write support soon, and I'm planning to start
implementing this as soon as I have time. Is there consensus on the
interface and/or the implementation?

I guess the detail/endian.hpp is complete, also for writing (using store
instead of load)?

 From earlier emails:

> IMHO, general rule should be this:
> read_{format} accepts std::basic_istream
> write_{format} accepts std::basic_ostream
> On the other hand, I quite like the iterator-based interface of Boost.Spirit
> and I think it would be easier to flip the idea over:
> - provide I/O interfaces based on iterators
> - allow users to pass streams through iterators
> instead of passing complete stream objects.
> Iterators are good for generalisation of both containers and streams.
> Bruno, what do you think?
> If we're rather talking about an iterator pair or a range then it
> makes things different and I agree it's a good choice (as opposed to
> explicitly taking a vector, a string or any specific container).

Best Regards,

Geometry list run by mateusz at