I think the distinction being made is maybe that in (say) Java trying to print on a closed filehandle object would throw an IOException which your code would be required to handle, whereas perl  -E 'close(STDOUT);say qq{FOOP}' will run (producing no output but also not printing any sort of error (although you could check the return from say and print $!)).

Of course if you "use warnings;", you will see the "print() on closed filehandle STDOUT" warning.

> Of course if you "use warnings;", you will see the "print() on closed filehandle STDOUT" warning.

and ...

Of course you can propagate warnings to die by changing $SIG{__WARN__} ;-)

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}

Actually I think I had the right intuition with Python.

They use exceptions for non-fatal communications like in

https://softwareengineering.stackexchange.com/questions/112463/why-do-iterators-in-python-raise-an-exception

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}

I see what you mean. I am just starting with Python. Instead of handling the exception, it appears that:


for value in some_iterable:
    print(value)
[download]

is the preferred syntax.

ok, so you found an exception. Well, kinda. There's no IO library function that corresponds to division.

Anyway, the point stands: Where other languages might use exception, Perl primarily returns false on error.

Update: Clearer wording

So you were only talking about IO and meant the lack of default to autodie?

Wasn't obvious to me.

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}

Of course you can create your own subs that throws exceptions, like autodie does. I don't know why you bring that up. I didn't talk about libraries at all except to say that Perl can throw exceptions.