Re^11: Perl Best Practices

in reply to Re^10: Perl Best Practices
in thread Perl Best Practices

Note that the errors arise when the exception disrupts the sequencing of side effects. No side-effects (like state), no problems.

All right. But AFAIK only pure functional programming avoids side-effects, isn't it? ;) How reimplementing the exemple above with no side-effects (in Perl, Java, Python, C++...) is beyond me.

Comment on Re^11: Perl Best Practices

Replies are listed 'Best First'.
Re^12: Perl Best Practices by Anonymous Monk on Jul 20, 2005 at 18:20 UTC
Well, when you write your own code in a language like Perl or Java, you can always try to minimize and localize side-effects. That is, you can try to make most of your functions pure, reduce the need for looping by using higher order functions, doing I/O at the top levels, not willy-nilly in the bowels, etc. When it comes to libraries though, you're at the mercy of someone else. Them's the breaks.	[reply]

Replies are listed 'Best First'.

Re^12: Perl Best Practices
by Anonymous Monk on Jul 20, 2005 at 18:20 UTC

Well, when you write your own code in a language like Perl or Java, you can always try to minimize and localize side-effects. That is, you can try to make most of your functions pure, reduce the need for looping by using higher order functions, doing I/O at the top levels, not willy-nilly in the bowels, etc. When it comes to libraries though, you're at the mercy of someone else. Them's the breaks.

[reply]

In Section Perl News