Comments on: Don’t Call it “Case Equality” http://www.pmamediagroup.com/2009/07/dont-call-it-case-equality/ Unique Marketing Techniques and Strategies with Guaranteed Results! Tue, 28 Jun 2011 15:49:44 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Earl Jenkins http://www.pmamediagroup.com/2009/07/dont-call-it-case-equality/comment-page-1/#comment-414 Earl Jenkins Thu, 05 Aug 2010 22:21:29 +0000 http://www.pmamediagroup.com/?p=956#comment-414 That last point about error rescue using === also begets the idea of defining === for a customer error class. For example, a JenkinsErrorCatcher class could define === as returning true for any Exception subclass that has a to_s that contains "Jenkins". Thus, we could have error handling based not just on class types, but also on any other exception data. (Of course, the example is lame, but the implications are huge.) Earl That last point about error rescue using === also begets the idea of defining === for a customer error class. For example, a JenkinsErrorCatcher class could define === as returning true for any Exception subclass that has a to_s that contains “Jenkins”. Thus, we could have error handling based not just on class types, but also on any other exception data.

(Of course, the example is lame, but the implications are huge.)

Earl

]]>