Bug #124789 for Getopt-Long: <> does not provide an object

Fri Mar 16 12:58:57 2018 SREZIC [...] cpan.org - Ticket created

Subject:

<> does not provide an object

The <> documentation states that the argument "is an object that stringifies to the argument name". But this does not seem to be the case anymore, since Getopt::Long 2.39 or so.

Mon Mar 19 04:33:30 2018 jv [...] cpan.org - Correspondence added

According to the comments in the source: # The arg to <> cannot be the CallBack object # since it may be passed to other modules that # get confused (e.g., Archive::Tar). Well, # it's not relevant for this callback anyway. It was even documented in the 2.39 CHANGES: * Passing an object as first argument to the callback handler for <> turned out to be a problem in cases where the argument was passed to other modules, e.g., Archive::Tar. Revert the change since the added functionality of the object is not really relevant for the <> callback function. However, it was not adjusted in the POD. This will be fixed. Thanks for pointing out.

Mon Mar 19 04:33:30 2018 The RT System itself - Status changed from 'new' to 'open'

Mon Mar 19 04:33:30 2018 jv [...] cpan.org - Taken

Mon Mar 19 04:40:25 2018 jv [...] cpan.org - Correspondence added

Fixed in the next release (2.51).

Mon Mar 19 04:40:25 2018 jv [...] cpan.org - Status changed from 'open' to 'resolved'