Hi all,
Project matgeom[1] has got lot more manageable than in the past, mostly thanks to your guidance and suggestions.
We are now facing a problem that, due to my lack of experience, I cannot solve in a sustainable way.
The situation:
Package geometry (extending matgeom)[2] developed a function called clipPolygon, and some time later the matgeom package developed a much unfeatured function with the same name
The problem:
When geometry is loaded it loads matgeom, and geometry::clipPolygon gets shadowed by matgeom::clipPolygon function, effectively degrading the functionality in geometry.
The solutions:
We have been discussing the following solutions:
1. ask upstream to rename matgeom:clipPolygon to matgeom:cropPolygon or any other less general name. This was not accepted so far[3]
2. With the upstream tracking system that I have set up, one can rename the matgeom::clipPolygon in the octave forge branch, and afaik, this will be propagated into the future. that is, git will remeber that the matgeom::clipPolygon was renamed some point int he past, so it will be alsways renamed even in the presence of updated to the matgeom function. I checked this and seems to be the case, but I wonder if this actually will not create future problems.
3. Complicate the loading/unloading of geometry package to rename/remove/quarantine matgeom::clipPolygon at loading time.
Do you have other suggestions ro concrete ways of doing 3 that are sustaibale/easy-to-maintain?
Thanks a lot
[1]:
--
JuanPi Carbajal
https://goo.gl/ayiJzi-----
“An article about computational result is advertising, not scholarship. The actual scholarship is the full software environment, code and data, that produced the result.”
- Buckheit and Donoho