and Idon't move neither up nor down from it (the best & the fastest
version)
Congratulations.
--
Steven
Am I turmoiling your wishful thinking?
You may nourish it till the end of time.
Python's "print a * b" gets Time Limit Exceeded.
=============================================
PHP's code
=============================================
fscanf(STDIN, "%d\n", &$tcs);
while ($tcs--) {
fscanf(STDIN, "%s %s\n", &$n, &$m);
echo bcmul($n, $m, 0)."\n";
}
=============================================
does it in 4.8s
Let us cease to nourish those fabled ones who dwell under bridges.
--
Tom Zych / freet...@pobox.com
Quidquid latine dictum sit, altum viditur.
LOL !
If speed is the only thing you care about, then you can forget about
fretting over whether 2.5 or 3.1 is faster. You're using the wrong
language to begin with.
Surely that depends on whether you care about execution speed or
development speed.
--
Steven
s/care/care more/. People generally care about both to /some/ extent.
(Probably being over-pedantic again...)
--
Tom Zych / freet...@pobox.com
"Would you like a lovely fluffy little white rabbit, little girl,
or a cutesy wootesly little brown rabbit?"
"Actually, I don't think my python would notice."
rr, is that you?
+1 QOTW.
Geremy Condra
Are you asking me?
If so, my account there is http://www.spoj.pl/users/zzz/
There's your problem. I'd say most Python 3.x adopters are using it
for something other than working out whose performance dick is the
longest.
In fairness, the Python Dev team is very aware of the risk of performance
degradation. Performance is important, but it is not *so important* that
it outweighs everything else.
The question that needs to be asked is not "Is Python 3 fast?", but
instead "Is Python 3 fast enough?".
--
Steven
Doing a lot of instrument control and data acquisition stuff.
And a short dev period has same importance as short run time.
As for the safety of those that dwell under and walk over
bridges, yes I wrote a strain gage calibrator system that was
used by a civil engr for monitoring a bridge.
I'm certainly not going to argue against that, I just don't find the
coding contortions used on sites like spoj.pl for performance gains to
be anything approximating real world code. I will happily sacrifice
weird performance trickery for language consistency or performance
stability any day.
But at the same time, I read every single article on PyPy's ongoing
development that I can :)