Mateusz Łoskot

What compiler and what version of the compiler is this `DEV-C + + 5.11` thing? What compilation flags did you use, especially what optimisations?

It's quite important to know at least if you do non-optimised debug build or you do optimised build (Release in Visual Studio speak).

Thanks for checking it's not optimisation related. > if I delete the "#define BOOST_GEOMETRY_NO_ROBUSTNESS", the answer will be correct. For some/many cases, that is what you should do, because without...

I don't have any uses of the DOI myself, but I can see it useful to others especially those who use and refer to Boost.Geometry in academic projects and papers....

AFAIK/U, typically `#include ` is supposed to import 100% definitions of Boost.XXX. Thus, I think, `#include ` should import all models, indeed.

Perhaps, if core/non-extension models are better not included via the `geometry.hpp` or other 'all-in-one' headers, it could be clearly documented as Boost.MP11 does it  (source https://www.boost.org/doc/libs/develop/libs/mp11/doc/html/mp11.html#mpl)

Moving this to milestone 1.76

I agree with @vissarion For reference, here is what PostGIS reports for the examples in question ```sql SELECT ST_GeomFromText('LINESTRING(1.0 2.0, \n 2.0 1.0)', 0); -- // fails -- ERROR: parse...

> I am using boost 1.70.0 and MSVC 2017 15.8 C++17. It would be helpful if you tried your case with Boost.Geometry from the current `develop` branch.

@AlastairHolmes Thank you for testing.