in reply to Re: runtime problem; elusive error
in thread runtime problem; elusive error

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
--
Andreas

Replies are listed 'Best First'.
Re^3: runtime problem; elusive error
by syphilis (Archbishop) on Sep 20, 2007 at 14:35 UTC
    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;
    Cheers,
    Rob