Re^8: Perl Best Practices

Replies are listed 'Best First'.
Re^9: Perl Best Practices by wazoox (Prior) on Jul 19, 2005 at 22:25 UTC
What do you mean? For me "mutable states" are stuff like loop indices. May you develop?	[reply]
Re^10: Perl Best Practices by Anonymous Monk on Jul 20, 2005 at 17:07 UTC
From the articles... Every time you call a function that can raise an exception and don't catch it on the spot, you create opportunities for surprise bugs caused by functions that terminated abruptly, leaving data in an inconsistent state, or other code paths that you didn't think about. ...and... `NotifyIcon CreateNotifyIcon() { NotifyIcon icon = new NotifyIcon(); icon.Text = "Blah blah blah"; icon.Visible = true; icon.Icon = new Icon(GetType(), "cool.ico"); return icon; }` [download] Here's what it might look like after you fix it to be correct in the face of exceptions: `NotifyIcon CreateNotifyIcon() { NotifyIcon icon = new NotifyIcon(); icon.Text = "Blah blah blah"; icon.Icon = new Icon(GetType(), "cool.ico"); icon.Visible = true; return icon; }` [download] Note that the errors arise when the exception disrupts the sequencing of side effects. No side-effects (like state), no problems.	[reply] [d/l] [select]
Re^11: Perl Best Practices by wazoox (Prior) on Jul 20, 2005 at 17:17 UTC
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.	[reply]
Re^12: Perl Best Practices by Anonymous Monk on Jul 20, 2005 at 18:20 UTC


No such thing as a small change
	PerlMonks