This starts failing on Perl v5.22:

$ perl -MTry::Tiny -e 'sub foo {sub{}} try {} catch \&foo->()'
Type of arg 1 to Try::Tiny::catch must be block or sub {} (not referen
+ce constructor) at -e line 1, at EOF
[download]

From perl5220delta:

The & prototype character now accepts only anonymous subs (sub {...}), things beginning with \&, or an explicit undef. Formerly it erroneously also allowed references to arrays, hashes, and lists. ... In addition, the \& prototype was allowing subroutine calls, whereas now it only allows subroutines: &foo is still permitted as an argument, while &foo() and foo() no longer are.

If you could show us the code that's causing the issue, I'm sure we can suggest an alternative that works on newer Perl versions.

Thanks monks!

False alarm. I needed to address the experimental push by casting my reference to array w/ @{}. It's in a different code block from try / catch block so I assumed the errors were unrelated (and they are) but fixing the one addresses the try / catch "issue".

Experimental push on scalar is now forbidden at [mymodule] line 474, n
+ear "$asset;"
Type of arg 1 to Try::Tiny::catch must be block or sub {} (not referen
+ce constructor) at [mymodule] line 680, near "};"
Type of arg 1 to Try::Tiny::try must be block or sub {} (not reference
+ constructor) at [mymodule] line 680, near "};"
[download]

I created short code sample below that illustrates the behavior in action (w/ the fix). Still not at all clear to me how the one (experimental push issue) affects the other, but I'm unblocked from making progress. Any thoughts?

use strict;
use warnings;
use 5.006;
use Try::Tiny;

my @array = ();
my $array_ref = \@array;

push $array_ref, 'test'; # bugbug
#push @{$array_ref}, 'test'; # <== change prev line to be like this

test();

sub test {
  try
  {
    my $a = 1/0;
  }
  catch
  {
    print 'awww, snap!';
  };

  1;
}

1;
__END__
[download]

Still not at all clear to me how the one (experimental push issue) affects the other, but I'm unblocked from making progress. Any thoughts?

I don't know for sure, but I'd suspect that the earlier error caused the parser to get confused about the rest of the program, that kind of thing happens often - one syntax error can leave the parser in a bad state, and while it may try to parse the rest of the program to report as many other errors as it can, it obviously got it wrong in this case. That's why short yet complete examples like the one you showed (thank you for that) are always incredibly useful, since if we'd known there were other errors in addition to the one you stated in the root node, the fix would have probably become obvious faster.

Please supply an SSCCE that produces the problem (or not, depending on Perl version).

I agree with AnomalousMonk that we'd need to see a short piece of example code that reproduces the issue, because I haven't been able to reproduce it myself, and I think it's a slightly strange issue.

Update: See Re: Try::Tiny complaining catch must be block or sub {} (not reference constructor).