* David Golden <xda...@gmail.com> [2009-11-18 16:05]: > So creating/destroying Perl objects -- even just for things > like argument passing on the stack -- is part of the cost of > the flexibility of Perl. When that becomes a bottleneck in > a tight loop, that's when XS becomes a potential option. > > That's not a knock on Perl -- that's just part of the design.
It isn’t inherent in the language design. A tracing JIT runtime *could* make Perl go faster than compiled code. (Unfortunately the Perl 5 spec is perl, so there can be no other runtime, and the one we have cannot be retrofitted with a JIT any time soon. Bah.) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
