On Mon, 13 Jun 2011, Jim Cromie wrote: > On Mon, Jun 13, 2011 at 1:18 PM, Todd Rinaldo <toddr@cpanel.net> wrote: > > I believe your patch to make these public was considered > > insufficient because the items were not documented along side > > making them public again. As I read it, this is what needs to be > > stepped up on. > > > > We're just talking about some POD here right? > > > > probly some XS-APITest additions too No need to guess, you could have checked Reini's original submission. Tests and docs are all there: https://github.com/rurban/perl/commit/3691eaa79cc6a196b6a424b4c7abc6c8f5a481e2 The issue (as far as I am concerned) is that none of the porters has "blessed" the now documented API as something they want to support going forward. Instead I read that Nicholas has a plan to implement a proper API for this kind of functionality. So I think we are all waiting for this to happen. Exporting the current symbol in maintenance branches is a completely separate issue. Personally I don't see a big issue with it, as it can't possibly break other code; it simply exports an additional symbols that is already exported on most platforms anyways, although technically this may not be covered by our maintenance policy. The biggest issues is that it will create the expectation that the symbol will continue to be exported in newer releases. This should cease to be a problem once the new API materializes. Cheers, -JanThread Previous | Thread Next