Sebastian Riedel [EMAIL PROTECTED] wrote:
Attached patch should fix that all.
Thanks, applied - just updated the sample conf.
leo
Sebastian Riedel [EMAIL PROTECTED] wrote:
The attached patch adds this, conf files now look so:
parrot: /home/sri/parrot/parrot: .pasm .imc
Good.
ruby: /usr/bin/ruby: .rb
python: /usr/bin/python: .py
python-C: /usr/bin/python -C: .py
^
That's probably parrot-C, anyway:
Output
Leopold Toetsch wrote:
Sebastian Riedel [EMAIL PROTECTED] wrote:
The attached patch adds this, conf files now look so:
parrot: /home/sri/parrot/parrot: .pasm .imc
Good.
ruby: /usr/bin/ruby: .rb
python: /usr/bin/python: .py
python-C: /usr/bin/python -C: .py
^
That's
leo wrote:
Any one out there, who speaks ruby and can translate tests, for which
we have a '.pl' file?.
just catched up mail and thought a bit practice might not be bad...
i intentionally did not wrote them optimal (performance-wise), but rather
elegantly (sort of ;).
thus this is only a
Sebastian Riedel [EMAIL PROTECTED] wrote:
The attached version should do most of the things you wanted.
I've now added parrotbench.pl (slightly modifed) to the CVS tree.
thanks,
leo
Ibotty [EMAIL PROTECTED] wrote:
just catched up mail and thought a bit practice might not be bad...
i intentionally did not wrote them optimal (performance-wise), but rather
elegantly (sort of ;).
Yeah, that's always the problem. Where applicable, we could add a set of
optimized versions.
Leopold Toetsch wrote:
Sebastian Riedel [EMAIL PROTECTED] wrote:
Sebastian Riedel wrote:
The attached version should do most of the things you wanted.
[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
../parrotbench.conf
parrot perlpython ruby
A very basic newbeish question..
[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
../parrotbench.conf
parrot perlpython ruby
oo1 100%39% 23% -
oo2 100%40% 22% -
Are bigger numbers more desirable (as they would be if they
Abhijit A. Mahabal wrote:
A very basic newbeish question..
[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
../parrotbench.conf
parrot perlpython ruby
oo1 100%39% 23% -
oo2 100%40% 22% -
Are bigger numbers more desirable
At 10:10 PM +0100 3/8/04, Sebastian Riedel wrote:
Abhijit A. Mahabal wrote:
A very basic newbeish question..
[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
../parrotbench.conf
parrot perlpython ruby
oo1 100%39% 23% -
oo2 100%40% 22%
Dan Sugalski wrote:
At 10:10 PM +0100 3/8/04, Sebastian Riedel wrote:
Abhijit A. Mahabal wrote:
A very basic newbeish question..
[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
../parrotbench.conf
parrot perlpython ruby
oo1 100%39% 23% -
oo2
At 11:04 PM +0100 3/8/04, Sebastian Riedel wrote:
Dan Sugalski wrote:
At 10:10 PM +0100 3/8/04, Sebastian Riedel wrote:
Abhijit A. Mahabal wrote:
Can we add a caption to the output? Otherwise I'll end up forgetting.
Will be added in the next version.
Cool, thanks.
We also need to implement a
Sebastian Riedel [EMAIL PROTECTED] wrote:
objective-ook? - SCNR
Attached is a quick'n dirty parrotbench, instead of a complicated
test harness it uses bash to make time measurements, so that
new languages are very simple to add.
bash isn't
Leopold Toetsch wrote:
Sebastian Riedel [EMAIL PROTECTED] wrote:
objective-ook? - SCNR
:)
Attached is a quick'n dirty parrotbench, instead of a complicated
test harness it uses bash to make time measurements, so that
new languages are very
Sebastian Riedel wrote:
Leopold Toetsch wrote:
Sebastian Riedel [EMAIL PROTECTED] wrote:
objective-ook? - SCNR
:)
Attached is a quick'n dirty parrotbench, instead of a complicated
test harness it uses bash to make time measurements, so that
new
Sebastian Riedel wrote:
I studied the config system, and now i wonder if it would make sense
to write a configure step to probe for enemies, or is that overkill?
Overkill doesn't even begin to describe it.
It ought not to be too difficult to look for enemies at the beginning
of your little
I'd a short look at perlbench from CPAN. This inspired me to the
following idea:
examples/benchmarks/* has a bunch of programs e.g.
oo1.pasm
oo1.pl
oo1.py
stress.pasm
stress.pl
...
Now like perlbench is able to compare run times of different perl
versions, the goal of this task is
Hi Leo,
Attached is a quick'n dirty parrotbench, instead of a complicated
test harness it uses bash to make time measurements, so that
new languages are very simple to add.
Currently it's just a proof of concept but if you like it i will make
a better version with pretty printing, extended
18 matches
Mail list logo
