We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At least two places in OpenSIPS where "use UNIVERSAL" is used:
modules/perl/lib/perl/OpenSIPS/LDAPUtils/LDAPConnection.pm 55:use UNIVERSAL qw( isa ); 188: if( isa($conf ,"OpenSIPS::LDAPUtils::LDAPConnection") ) {
modules/perl/lib/perl/OpenSIPS/VDB.pm 48:use UNIVERSAL qw ( can ); 90: if (can($pkg, $3)) { 92: } elsif (can($v, "init")) { 95: } elsif (can($v, "new")) {
This should be fixed as according to this document it will throw a fatal error starting with Perl 5.22:
http://search.cpan.org/~shay/perl-5.21.11/pod/perl5213delta.pod#use%C2%A0UNIVERSAL%C2%A0%27...%27_is_now_a_fatal_error
The text was updated successfully, but these errors were encountered:
Hello,
Please apply the attached patch. UNIVERSAL-import-deprecated.diff.zip
Sorry, something went wrong.
@devjunix thanks for the patch!
Committed in e5f0b55, all the way to 1.11.
1.11
Fix "use UNIVERSAL" is a fatal error since perl 5.22 following http:/…
5a369ad
…/search.cpan.org/~shay/perl-5.22.1/lib/UNIVERSAL.pm documentation Bug: OpenSIPS#804
No branches or pull requests
At least two places in OpenSIPS where "use UNIVERSAL" is used:
modules/perl/lib/perl/OpenSIPS/LDAPUtils/LDAPConnection.pm
55:use UNIVERSAL qw( isa );
188: if( isa($conf ,"OpenSIPS::LDAPUtils::LDAPConnection") ) {
modules/perl/lib/perl/OpenSIPS/VDB.pm
48:use UNIVERSAL qw ( can );
90: if (can($pkg, $3)) {
92: } elsif (can($v, "init")) {
95: } elsif (can($v, "new")) {
This should be fixed as according to this document it will throw a fatal error starting with Perl 5.22:
http://search.cpan.org/~shay/perl-5.21.11/pod/perl5213delta.pod#use%C2%A0UNIVERSAL%C2%A0%27...%27_is_now_a_fatal_error
The text was updated successfully, but these errors were encountered: