Skip Menu |

This queue is for tickets about the XML-XSH CPAN distribution.

Report information
The Basics
Id: 105231
Status: rejected
Worked: 5 min
Priority: 0/
Queue: XML-XSH

People
Owner: CHOROBA [...] cpan.org
Requestors: ether [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 1.8.4



Subject: use of deprecated defined(@array)
In newer perl versions: defined(@array) is deprecated at .../XML/XSH/Completion.pm line 111. (Maybe you should just omit the defined()?)
Use XML::XSH2 instead of XML::XSH, the problem has already been fixed there. BTW, what's the recommended way of deprecating a module in favour of a new version? Ch. On Sun Jun 14 22:06:30 2015, ETHER wrote: Show quoted text
> In newer perl versions: > > defined(@array) is deprecated at .../XML/XSH/Completion.pm line 111. > (Maybe you should just omit the defined()?)
On 2015-06-15 02:50:09, CHOROBA wrote: Show quoted text
> Use XML::XSH2 instead of XML::XSH, the problem has already been fixed > there. BTW, what's the recommended way of deprecating a module in > favour of a new version? > > Ch. > > On Sun Jun 14 22:06:30 2015, ETHER wrote:
> > In newer perl versions: > > > > defined(@array) is deprecated at .../XML/XSH/Completion.pm line 111. > > (Maybe you should just omit the defined()?)
Add 'x_deprecated => 1' to metadata, add '(DEPRECATED)' to the distribution's abstract (in metadata, and the main module's pod), and document the successor module.
On Mon Jun 15 12:36:14 2015, ETHER wrote: Show quoted text
> On 2015-06-15 02:50:09, CHOROBA wrote:
> > Use XML::XSH2 instead of XML::XSH, the problem has already been fixed > > there. BTW, what's the recommended way of deprecating a module in > > favour of a new version? > > > > Ch. > > > > On Sun Jun 14 22:06:30 2015, ETHER wrote:
> > > In newer perl versions: > > > > > > defined(@array) is deprecated at .../XML/XSH/Completion.pm line > > > 111. > > > (Maybe you should just omit the defined()?)
> > > Add 'x_deprecated => 1' to metadata, add '(DEPRECATED)' to the > distribution's abstract (in metadata, and the main module's pod), and > document the successor module.
Done. Ch.