Re^2: runtime problem; elusive error

Looks like the "workaround" would be (removing the @Vals) line, as that hides the errormy $_debug_ops = (0 | DBG_RAND | DBG_KEYS |DBG_INFO); That puts in numeric context...sigh. Sometimes I'd like to be able to put a "numeric" or "string" in front a var to let it know what I want. The alternative is use something of the appropriate type (num or string), first, but that's not nearly so clear as being able to put in a "numeric" , like one does with "scalar", now.

Thanks for the heads up...I'd report it as a but, but not sure how they'd fix it -- though I sure don't know why it's returning "=28" (hex equiv to left paren).

It's interesting that the XS version is consistent (i.e. same constant).

Comment on Re^2: runtime problem; elusive error Download Code

Replies are listed 'Best First'.
Re^3: runtime problem; elusive error by almut (Canon) on Sep 20, 2007 at 17:44 UTC
though I sure don't know why it's returning "=28" That's the bitwise string-OR of the stringified decimal representations of the three values, i.e. `"128" \| "8" \| "4"` [download] or, more eplicitly `chr(ord('1') \| ord('8') \| ord('4')) . # '=' chr(ord('2') \| ord('') \| ord('') ) . # '2' chr(ord('8') \| ord('') \| ord('') ) # '8'` [download]	[reply] [d/l] [select]
Re^3: runtime problem; elusive error by ikegami (Patriarch) on Sep 20, 2007 at 19:16 UTC
I'd like to be able to put a "numeric" or "string" in front a var to let it know what I want You can. They are spelled "`0+`" and "`''.`" respectively. `my $x = '8'; my $y = '16'; print((0+$x) \| (0+$y), "\n"); # 24 print((''.$x) \| (''.$y), "\n"); # 96` [download] Update: Oops, that doesn't quite answer your question. If the variable wasn't read-only, you could do the following: `$x .= ''; # Stringify $x += 0; # Numerify` [download]	[reply] [d/l] [select]