<br><br><div><span class="gmail_quote">On 9/27/07, <b class="gmail_sendername">Jonas Pfenniger</b> <<a href="mailto:zimbatm@oree.ch">zimbatm@oree.ch</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2007/9/27, Gregor Schmidt <<a href="mailto:ruby@schmidtwisser.de">ruby@schmidtwisser.de</a>>:<br>> Defining NilClass#method_missing for nothing is not too clever, for a<br>> large scale libary IMO.<br><br>I'm not sure you understood, it is ruby2ruby who defined
<br>nil.method_missing. We can't start to support each and every hack a<br>library will add to the Ruby core.</blockquote><div><br><br>^for this reason, you can't really use ruby2ruby in anything serious. nil.method_missing
prevents a lot of exceptions from being thrown, and there's a lot of code out their that legitimately needs those exceptions to be thrown for correct behavior.<br><br><br></div><br></div><br>