David Vavra

Well, so $\ = "\n" it is. (Why) do you need it? The short answer is because I do. I might point out that, in the meantime, I've been using Devel::ptkdb which doesn't have this limitation. It seems strange to have to write code around the debugger's tastes. It should at least be documented so the writing-around can be accomplished. Are there any other debugger preferences that I should be aware of? I'd also suggest you use the JSON::XS module for JSON parsing Everybody's a critic :) I'm sure JSON::XS...

FWIW: I have PadWalker 2.3 installed.

Umm, that didn't get formatted well. Not sure how to get the vertical bars to display,

The debugger consol is displaying the value. use strict; use JSON::Parse ':all'; $\ = "\n"; $,= ' '; my $jsonFile = "/tmp/odds.json"; my $prl = json_file_to_perl ($jsonFile); Debug Console output: 15: my $prl = json_file_to_perl ($jsonFile); DB<10> ;{ do 'dumpvar_epic.pm' unless defined &dumpvar_epic::dump_lexical_vars; my $offset = 0; my $savout = CORE::select($DB::OUT); dumpvar_epic::dump_lexical_vars($offset); CORE::select($savout); }; 9 $jsonFile 1 1 17 SCALAR(0x2437ec8) 16 '/tmp/odds.json' 2...

Can't view variables when debugging

FWIW, I have a similar problem. I've discovered that if $\ is undefined then I can...

FWIW, I have a similar problem. I've discovered that if $\ is undefined then I can...

FWIW, I have a similar problem. I've discovered that if $\ is undefined then I can...