in reply to runtime problem; elusive error

The bug may disappear if you install Readonly::XS ... not sure - just a thought.

Readonly::XS provides about the simplest way there is of making scalars readonly. (Note that you don't explicitly "use Readonly::XS;". You just install it and Readonly will automatically use it for making scalars readonly.)

Cheers,
Rob

Replies are listed 'Best First'.
Re^2: runtime problem; elusive error
by andreas1234567 (Vicar) on Sep 20, 2007 at 12:54 UTC
    Doesn't look like installing Readonly::XS helps: 
    use warnings;
use strict;
use Readonly;
use Readonly::XS;

Readonly my $DBG_INFO    => 0x0004;
Readonly my $DBG_KEYS    => 0x0008;
Readonly my $DBG_RAND    => 0x0080;

Readonly my $_debug_ops => ($DBG_RAND | $DBG_KEYS | $DBG_INFO);
printf ("%04x\n", $_debug_ops);
printf ("%04x\n", $DBG_RAND | $DBG_KEYS | $DBG_INFO);

__END__
$ perl -wl 640089.pl
Argument "=28" isn't numeric in printf at 640089.pl line 12.
0000
008c

Readonly is up to date (1.03).
Readonly::XS is up to date (1.04).
perl, v5.8.5
linux 2.6.9

    [download]
    --
    Andreas
[reply]
[d/l]
      Doesn't look like installing Readonly::XS helps

      Then I guess just Inline::C it: 
      use warnings;
use strict;

use Inline C => <<'EOC';

void ro_on(SV * x) {
     SvREADONLY_on(x);
}

EOC

my ($DBG_ANY, $DBG_INFO, $DBG_KEYS, $DBG_RAND)
    = (-1, 0x0004, 0x0008, 0x0080);

ro_on($_) for($DBG_ANY, $DBG_INFO, $DBG_KEYS, $DBG_RAND);

my $_debug_ops = $DBG_RAND | $DBG_KEYS | $DBG_INFO;

ro_on($_debug_ops);

printf "debugops = 0x%04x\n",$_debug_ops;

      [download]
      Cheers,
      Rob
[reply]
[d/l]

In Section Seekers of Perl Wisdom