[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47502] geometry or mapping package: polysplit
|
From: |
Juan Pablo Carbajal |
|
Subject: |
[Octave-bug-tracker] [bug #47502] geometry or mapping package: polysplit and polyjoin functions |
|
Date: |
Thu, 28 Apr 2016 20:59:38 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36 |
Follow-up Comment #6, bug #47502 (project octave):
Yeap, that's true. Sorry I missed that.
What do oyu mean with ND joinPolygons? geometry (matGeom) is 2D,3D geometry
package, so ND is out of the scope if you meant multiple dimensions.
Geometry is lagging behind matGeom and I am thinking to just submit all my
upgrades upstream and start cloning matGeom. It will be good to have somebody
checking the default branch to detect when I break backwards compatibility.
We can add the functions you deem necessary to geometry, no problem, as long
as they stay within the scope of the package.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47502>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/