Bug #75276 for Const-Fast: Const::Fast won't make top-level references read-only

Fri Feb 24 10:40:40 2012 brianski [...] cpan.org - Ticket created

Subject:

Const::Fast won't make top-level references read-only

_make_readonly() chases references, but the top level const() sub does not: $ perl -le 'use strict; use warnings; use Const::Fast; my $hashref = { "foo" => "bar", "baaz" => "quux" }; const($hashref => $hashref); ' Can't make variable readonly at -e line 1 $ perl -le 'use strict; use warnings; use Const::Fast; my $arrayref = [ 1, 2, 3, 4 ]; const($arrayref => $arrayref); ' Can't make variable readonly at -e line 1 ski@anito:~/mysrc/comma$ perl -le 'use strict; use warnings; use Const::Fast; my $val = 3; my $scalarref = \$val; const($scalarref => $scalarref);' Can't make variable readonly at -e line 1 $ perl -le 'use strict; use warnings; use Const::Fast; my $a = \{}; const($a => $a);' Can't make variable readonly at -e line 1 $ perl -le 'use strict; use warnings; use Const::Fast; my $a = bless( \ {}, "FOO" );const($a => $a);' Can't make variable readonly at -e line 1 ... etc. seems to me like this is a bug, or at least something that should be documented / overridable with an option to const().

Fri Feb 24 12:23:38 2012 brianski [...] cpan.org - Correspondence added

I now see this is because we are not using the preferred idiom: const my $a = {}; # or whatever The problem with this idiom is it doesn't support locking a variable after performing some basic operations on it, for example: my %foo; $foo{...} = ... for (...); const(%foo); Any thoughts on supporting such usage? Thanks, Brian Szymanski On Fri Feb 24 10:40:40 2012, BRIANSKI wrote: Show quoted text

> _make_readonly() chases references, but the top level const() sub does > not: > > $ perl -le 'use strict; use warnings; use Const::Fast; my $hashref = { > "foo" => "bar", "baaz" => "quux" }; const($hashref => $hashref); ' > Can't make variable readonly at -e line 1 > > $ perl -le 'use strict; use warnings; use Const::Fast; my $arrayref =

[ Show quoted text

> 1, 2, 3, 4 ]; const($arrayref => $arrayref); ' > Can't make variable readonly at -e line 1 > > ski@anito:~/mysrc/comma$ perl -le 'use strict; use warnings; use > Const::Fast; my $val = 3; my $scalarref = \$val; const($scalarref => > $scalarref);' > Can't make variable readonly at -e line 1 > > $ perl -le 'use strict; use warnings; use Const::Fast; my $a = \{}; > const($a => $a);' > Can't make variable readonly at -e line 1 > > $ perl -le 'use strict; use warnings; use Const::Fast; my $a = bless(

\ Show quoted text

> {}, "FOO" );const($a => $a);' > Can't make variable readonly at -e line 1 > > ... etc. seems to me like this is a bug, or at least something that > should be documented / overridable with an option to const().

Fri Feb 24 12:23:39 2012 brianski [...] cpan.org - Status changed from 'new' to 'open'

Fri Feb 24 16:50:03 2012 LEONT [...] cpan.org - Correspondence added

On Fri Feb 24 10:40:40 2012, BRIANSKI wrote: Show quoted text

> _make_readonly() chases references, but the top level const() sub does > not: > > $ perl -le 'use strict; use warnings; use Const::Fast; my $hashref = { > "foo" => "bar", "baaz" => "quux" }; const($hashref => $hashref); ' > Can't make variable readonly at -e line 1 > > $ perl -le 'use strict; use warnings; use Const::Fast; my $arrayref = [ > 1, 2, 3, 4 ]; const($arrayref => $arrayref); ' > Can't make variable readonly at -e line 1 > > ski@anito:~/mysrc/comma$ perl -le 'use strict; use warnings; use > Const::Fast; my $val = 3; my $scalarref = \$val; const($scalarref => > $scalarref);' > Can't make variable readonly at -e line 1 > > $ perl -le 'use strict; use warnings; use Const::Fast; my $a = \{}; > const($a => $a);' > Can't make variable readonly at -e line 1 > > $ perl -le 'use strict; use warnings; use Const::Fast; my $a = bless( \ > {}, "FOO" );const($a => $a);' > Can't make variable readonly at -e line 1 > > ... etc. seems to me like this is a bug, or at least something that > should be documented / overridable with an option to const().

Yes, this is a bug, thanks for the report. It has been fixed in Const::Fast 0.011. Leon

Fri Feb 24 19:37:00 2012 LEONT [...] cpan.org - Status changed from 'open' to 'resolved'