On Wed, Jun 3, 2009 at 9:01 PM, Daniel Carrera
daniel.carr...@theingots.org wrote:
Hi Chris,
In addition to Patrick's excellent reply, I'd like to mention that one way
to help the project is to just write code in Perl 6. This is a good way to
find bugs, including performance bugs.
I have
Joshua Gatcomb wrote:
I know these benchmarks have their value, but I am more interested in
real practical code that I have previously written to solve a problem.
I know that the Rakudo code will be slower than the perl 5.
The point of the benchmark is not oh look, it's slower than Perl 5.
On Thu, Jun 4, 2009 at 11:16 AM, Daniel Carrera
daniel.carr...@theingots.org wrote:
The point of the benchmark is not oh look, it's slower than Perl 5. The
benchmarks are good for testing a specific aspect of the language, so it is
easier to isolate *where* the problem is. This is harder on a
Joshua Gatcomb wrote:
I think you are confusing profiling with benchmarking. Profiling
helps you identify where a problem is. Benchmarking helps you compare
two different versions of the same routine.
Whatever. I have a series of programs that test the speed of various
aspects of the
