[prev] [thread] [next] [lurker] [Date index for 2007/01/29]
On 29 Jan 2007, at 17:26, Peter da Silva wrote: > A GUI is an asynchronous environment, you have to have a mechanism > to deal with it. This is a good one... in that context. Yes, sure - but their use is in no way limited to async environments. >> So how are you proposing to propagate recoverable errors? Guard >> every function call with a conditional? > > In many cases, yes. And, I've found that you have to put an > exception handler around pretty much every function call that's > potentially the source of a "routine" exception anyway. Why? You should be able to ignore exceptions that you don't explicitly need to know about and allow them to propagate higher up the call chain. >>> I wouldn't class closures in with signals and callbacks, but I've >>> mostly dealt with closures where they're basically generators. It >>> wouldn't surprise me to learn that there's hatefulness lurking >>> there. > >> Your world scares me. > > What's wrong with generators? Nothing. I was referring to "It wouldn't surprise me to learn that there's hatefulness lurking there." :) -- Andy Armstrong, hexten.netThere's stuff above here
Generated at 23:01 on 06 Feb 2007 by mariachi 0.52