You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When PPI::Tokenizer method all_tokens() finds an error, it sets $@ to a PPI::Exception which has its $err->message as another PPI::Exception. Is that meant to be so? It has the unhappy effect of meaning $err->message after all_tokens() is not textual but say "PPI::Exception=HASH(0x814b9704)".
Sample program below illustrating $err->message->message to get the text of the error.
When PPI::Tokenizer method all_tokens() finds an error, it sets $@ to a PPI::Exception which has its $err->message as another PPI::Exception. Is that meant to be so? It has the unhappy effect of meaning $err->message after all_tokens() is not textual but say "PPI::Exception=HASH(0x814b9704)".
Sample program below illustrating $err->message->message to get the text of the error.
foo.pl.txt
The text was updated successfully, but these errors were encountered: