Working on it a little :) and I would like Blair's 3 am pepper extract
(50 USD).
Kartik Thakore
On 23-Nov-09, at 1:47 AM, Jonathan Leto jal...@gmail.com wrote:
Howdy,
I seem to recall that we have a pressing need for another perl5 VM to
deliver on the promise of being able to run your
Howdy,
I seem to recall that we have a pressing need for another perl5 VM to
deliver on the promise of being able to run your perl5 code in perl6
programs.
--Eric
This is called Blizkost [0], a project stared by Jonathan Worthington
[1], one of the core Rakudo developers. It allows Parrot
* On Wed, Nov 18 2009, Aristotle Pagaltzis wrote:
* 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
# from Jonathan Rockway
# on Thursday 19 November 2009 07:06:
The real reason for the lack of another Perl VM is that Perl
programmers are very, very lazy. ;)
In this case, you mean 'perl' programmers. :-D
I seem to recall that we have a pressing need for another perl5 VM to
deliver on the
Quoth enoba...@gmail.com (Eric Wilhelm):
# from Jonathan Rockway
# on Thursday 19 November 2009 07:06:
The real reason for the lack of another Perl VM is that Perl
programmers are very, very lazy. ;)
In this case, you mean 'perl' programmers. :-D
I seem to recall that we have a
Dear Module Authors,
recently in one of the Amsterdam Perl Mongers meetings the question came up
how much faster actually the XS version of Date::Calc (Date::Calc::XS) was
as compared to the Pure Perl version (Date::Calc::PP).
Here is the answer (see attached script - you will need to have
* O. STeffen BEYer ost...@gmail.com [2009-11-18 13:10]:
One can see from these results that the XS version quite
consistently runs approximately about 15 times faster than the
PP version.
This is flame bait? Why is this flame bait?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
Maybe he thought there were a debate on XS v.s PP performance. If only
we could be this flame retardent in the uneeded perl5 v.s perl6 debate.
Kartik Thakore
On 18-Nov-09, at 7:29 AM, Aristotle Pagaltzis pagalt...@gmx.de wrote:
* O. STeffen BEYer ost...@gmail.com [2009-11-18 13:10]:
One
It might be seen as flame bait because there have been endless discussions
on the Perl vs. C execution speed issue on Perl newsgroups in the past.
:-)
2009/11/18 Kartik Thakore thakore.kar...@gmail.com
Maybe he thought there were a debate on XS v.s PP performance. If only we
could be this
Steffen-
As always, I think benchmarks are important. As you've shown below, in
your case, the XS implementation certainly is faster. I think it all
depends on whether the speed of the system is bound by external
factors (like disk speed, speed of a network stream) or your CPU.
Certainly I've
On Wed, Nov 18, 2009 at 9:20 AM, Jonathan Yu jonathan.i...@gmail.com wrote:
Certainly I've found for tight loops with lots of calculations, XS/C
is going to be faster. Why? Because it's compiled into machine code
and executed directly on the chip. On the other hand, Perl is compiled
into
Aristotle Pagaltzis wrote:
This is flame bait? Why is this flame bait?
well, if nothing else works, this could easily be turned into a
Date::Calc vs. DateTime flame bait :-)
cheers,
Aldo
* 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.
13 matches
Mail list logo
