[Octave-patch-tracker] [patch #9000] Polygon functions for geometry/mapping package

[Philip Nienhuis]

Follow-up Comment #7, patch #9000 (project octave):

Good that geometry accepts both vectors and matrices, I wasn't aware of it
(didn't pay due attention :-) ).

There's no specific reason to combine the two modes of polyclip, other than
that the mexclipper routine (enclosed in the Clipper library download) also
implemented it this way.
It is not all that hard to strip polyclip.m but why bother? It isn't quite in
the way.

Would you rather accept ispolycw from
http://octave.1599824.n4.nabble.com/GSoC-16-Sample-implementation-for-ispolycw-function-tc4675763.html
into geometry? Looking a bit closer it is a fully binary module w/o wrappers
so I expect it to be the fastest.

Boost:Geometry comprises merely headers; I wouldn't know how to make this into
an external dependency but as there's no compilation involved it can't be
hard. I suppose those headers should end up somewhere in /usr/include/boost.
In principle, similar goes for Clipper; but as it happens Clipper has been
turned into just 2 mex cpp files that are far more easily put in an OF
package. I can't imagine any other package to depend on Clipper and if there
are the geometry package can be made a dependency.

Next week I'll have a bit more time to really assist with coding. I first want
to make a new io release after fixing bug #48025


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?9000>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/