From: Neil Stevens Date: 2008-12-05T08:13:22+09:00 Subject: [ruby-core:20337] Re: Behavior: autoload calls rb_require() directly This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig63D13B7BBA500DFD4966BF7D Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Charles Oliver Nutter wrote: > daz wrote: >> Sorry, that's wrong. >> >> Like Pit just suggested elsewhere in this thread, we can't override to= >> log (a, :plus, b) then a._oldplus_(b). >> >> The design is short-circuited ... *not* optimized. >> >> A language designer shouldn't test her abilities to second guess what >> the user is likely to want or need to do. It's a lost cause. :) >=20 > I wasn't speaking as a language designer or an implementer; I was > speaking as someone who'd like to be able to get C-like performance out= > of numeric operations in Ruby some day. Yes, it's still possible. But s= o > is draining the ocean with an eyedropper. Yup. Using the wrong tool for a job is usually inefficient. There are already languages out there that sacrifice flexibility in order to give efficiency for niche tasks. I don't understand why Ruby should start to become one of them. --=20 Neil Stevens - neil@hakubi.us If you're seeing shades of gray, it's because you're not looking close enough to see the black and white dots. --------------enig63D13B7BBA500DFD4966BF7D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFJOGPkf7mnligQOmERAl66AKCOXgc2NxXA7htmewUnRzSHmGI4rgCgkoYN jwJobUWt5rpuwx8uaRJEhi8= =xUhG -----END PGP SIGNATURE----- --------------enig63D13B7BBA500DFD4966BF7D--