New issue
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
Two DB::lsub oddities #13264
Comments
From @cpansproutDB::sub has to exist for DB::lsub to be called. #!perl -d:Peek #!perl -d:Peek Why this limitation? Also, if DB::sub is defined, then DB::lsub lookup autovivifies %DB::lsub (the hash), even if &DB::lsub is not defined. It has been this way since 1ad62f6 added support for lsub. #!perl -d:Peek sub DB::DB {} sub foo:lvalue{} Why on earth is that hash being vivified? What is it for? Flags: Site configuration information for perl 5.19.4: Configured by sprout at Mon Sep 9 00:16:24 PDT 2013. Summary of my perl5 (revision 5 version 19 subversion 4) configuration: @INC for perl 5.19.4: Environment for perl 5.19.4: |
From @cpansproutOn Sun Sep 15 13:27:04 2013, sprout wrote:
That part of this ticket is fixed in 07b605e. -- Father Chrysostomos |
From [Unknown Contact. See original ticket]On Sun Sep 15 13:27:04 2013, sprout wrote:
That part of this ticket is fixed in 07b605e. -- Father Chrysostomos |
From zefram@fysh.orgFather Chrysostomos wrote:
It might perhaps be in order to avoid making sub calls any more expensive In the case of an lvalue sub there'd also be the extra cost of looking -zefram |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#119811 (status was 'open')
Searchable as RT119811$
The text was updated successfully, but these errors were encountered: