[prev] [thread] [next] [lurker] [Date index for 2007/01/29]
On Jan 29, 2007, at 9:50 AM, Andy Armstrong wrote: > http://doc.trolltech.com/3.3/signalsandslots.html Ah, rendezvous-style messages. A GUI is an asynchronous environment, you have to have a mechanism to deal with it. This is a good one... in that context. >> Exceptions should be reserved for errors that aren't normally >> recovered from. It should require the equivalent of "#pragma >> FIXME_THIS_IS_EVIL_CODE" to do anything at the end of an exception >> handler other than throwing the same exception again. > 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. It's not exceptions that are hateful, per se, it's the use of exceptions for non-exceptional failures. That's why I didn't say "Exceptions should be reserved for non-recoverable errors", by the way. >> 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?
Generated at 23:01 on 06 Feb 2007 by mariachi 0.52