Deparse feature and Moose

[zenogantner]

The "Deparse" feature and Moose behave a bit strangely when they are combined.

See the attached screenshot.

Deparse basically reports three empty lines.
But my guess is that actually things do happen here, right?

[szabgab]

Deparse saves the selection in a file and then calls this:

perl -MO=Deparse,-p some_file.pl

Could you try that outside of Padre and see what does that return?

[zenogantner]

The output for {{text.pl}}} is

String found where operator expected at /home/mrg/text.pl line 1, near "has 'formatter'"
	(Do you need to predeclare has?)
String found where operator expected at /home/mrg/text.pl line 2, near "has 'summary_table_type'"
	(Do you need to predeclare has?)
String found where operator expected at /home/mrg/text.pl line 3, near "has 'table_columns'"
	(Do you need to predeclare has?)
String found where operator expected at /home/mrg/text.pl line 5, near "has 'table_caption'"
	(Do you need to predeclare has?)
String found where operator expected at /home/mrg/text.pl line 7, near "has 'table_format'"
	(Do you need to predeclare has?)
String found where operator expected at /home/mrg/text.pl line 9, near "has 'key_rule_ref'"
	(Do you need to predeclare has?)
String found where operator expected at /home/mrg/text.pl line 10, near "has 'value_rule_ref'"
	(Do you need to predeclare has?)
String found where operator expected at /home/mrg/text.pl line 11, near "has 'new_pair_rule_ref'"
	(Do you need to predeclare has?)
syntax error at /home/mrg/text.pl line 1, near "has 'formatter'"
/home/mrg/text.pl had compilation errors.
;
;
;
;
;
;

[bowtie]

zeno

I think this works for me with in Padre 0.97 using

Padre::Plugin::Nopaste::Services

can you take a look

I hope it helps in finding a solution, or scope