On 1 October 2017 at 21:01, Alan W. Irwin <ir...@beluga.phys.uvic.ca> wrote: > On 2017-10-01 09:49+0100 Phil Rosenberg wrote: > > [Alan said] >>> >>> With regard to your remark concerning writing a plsfillrule() function >>> and systematically using it throughout src/plargs.c, I wouldn't want >>> to do that myself, but if you or Jim want to make such a change and it >>> passes comprehensive testing, I certainly would not object. >> >> > [Phil responded] >> >> I can add a new API function if you think it is useful, but I can only >> propagate it as far as the C and C++ APIs, someone else would have to >> propagate it to other languages as needed. >> > > From what has been said, my impression is a plsfillrule() function is > C-only functionality to make src/plargs.c easier to understand and use > correctly. If that impression is correct there should be no need to > propagate this functionality even to our C++ binding since all our bindings > simply wrap the C plparseopts routine without knowing its > internal implementation details. But please educate me if that > impression is incorrect. >
Hi Alan I actually meant, do we want to add plsfillrule as an API function? It feels more like it should be an API function rather than a command argument. It would be little trouble to allow users to swap back and forward between the two rules. But I have a feeling this functionality is not used that often so maybe it's not worth the effort. Phil ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
