[geos-devel] [UTF] envelope_class_test.cpp fixed for Boost 1.33

[Mateusz Łoskot]

Mateusz Łoskot wrote:
> Paul Ramsey wrote:
> 
>> The situation in general makes me wary, if Boost is going to changing
>>  incompatibly with some regularity.
> 
> 
> Yes, I also have similar thoughts.
> Honestly, I'm a bit surprised that some Boost library can break 
> compatibility between releases 1.33 and 1.34.
> I have to discuss it with Gennadyi Rozental - the author of Boost.Test


So, as Gennadiy has explained me, Boost is backward compatible, but not 
forward. It's safe to use older API from Boost 1.33.

Complete story I'd suggest to take a look at is here,

http://thread.gmane.org/gmane.comp.lib.boost.user/17409


Now, I don't want to make much commotion about tests, and if we've just 
decided to go on with TUT that's OK for me.

But my next question is more about GEOS future. Should be Boost 
considered or not?
As we discussed it much with Sandro and Norman on the #postgis channel,
in future it would be nice to move to modern C++, so then I suppose it's 
not possible to drop Boost (I mean without huge amount of work :-)).
So, I'm trying to convince myself about that Boost is still good piece 
of software and worth to use.

If I'd like to redesign "something" in GEOS, rewrite in more 
safe/short/elegant way then how should I do it to provide useful code?
Is this OK if I'll use Boost e.g. it's Smart Pointers or other stuff.

Please, give me some light about potential possibilities for future GEOS 
development.

Cheers
-- 
Mateusz Łoskot
http://mateusz.loskot.net