NotFound wrote:
But if you talk about perl6, this is not applicable, the perl6
function can have any wanted signature, it will never call the
function directly, it emits the opcode that will call it and can
insert any check or change of his argument. If the sub implementation
allows accidental
I applied for an account and built what seems to me to be an appropriate
Parrot Testing Status page. My proposed link target is
http://www.parrot.org/wiki/some-testing-status-tools . If someone wants
to set me up as a site editor I will fix the link myself otherwise the
page is available for
Michael Peters wrote:
Ronald Schmidt wrote:
I've been meaning to update that wiki page to point to the progress
we're making toward this. I should also write up how Smolder already
accomplishes those goals (well, the ones it does accomplish).
Thanks. If I had noticed that smolder
I am posting this message to one more mailing list for a few reasons,
but mostly to request that some notice of the work be placed on the
project’s request page, RFP: Parrot needs better smoke reports, if the
results are found to make an adequate contribution the Queryability of
smoke reports.
Vasily Chekalkin wrote:
This is wrong patch. eval() shouldn't throws any exceptions.
Correct patch for 'eval()' and Test.pm attached.
As Mr Lenz wrote with respect to eval exceptions and this patch:
Are there any exceptions that are not caught by eval?
Currently rakudo seems to catch
