Re^6: Try::Tiny and -E

Does it really make sense to make all Try::Tiny-using application start issuing warnings just by upgrading to Perl 5.40?

I agree that this shouldn't be for Try::Tiny to address (except in documentation).

Comment on Re^6: Try::Tiny and -E

Replies are listed 'Best First'.
Re^7: Try::Tiny and -E by CountZero (Bishop) on Jan 06, 2026 at 12:52 UTC
I would prefer a warning rather than have the program crash without a proper explanation. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics	[reply]
Re^8: Try::Tiny and -E by ikegami (Patriarch) on Jan 07, 2026 at 15:33 UTC
But programs that use Try::Tiny don't crash just because `perl` 5.40 is used. What you suggested would make every program that uses Try::Tiny start warning even when there's absolutely no issue.	[reply] [d/l]
Re^9: Try::Tiny and -E by CountZero (Bishop) on Jan 08, 2026 at 13:56 UTC
True,but I find that a small price to pay for peace of mind. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics	[reply]