On 2017-01-17 21:35, Will Coleda wrote:
> If you'd like to turn this into a doc-u-bug, that's fine; please open
> a ticket at
>
> https://github.com/perl6/doc/issues
Already done and described on earlier timestamp on ticket "Mon, 16 Jan
2017 11:12:59 -0800" by AlexDaniel++
https://github.com/p
Please try removing the parrot and parrot_install directories and try
the --gen-parrot option again and let me know if that changes the
failure mode.
No luck.
I removed both directories, reset the build\PARROT_VERSION to 44371, ran
"perl Configure.pl --gen-parrot" followed by "mingw32-m
Will Coleda wrote:
Was there an old copy of parrot around from a previous build of rakudo?
If so, you might want to move aside the D:\Src\rakudo\parrot*
directories and rebuild parrot using the appropriate rakudo
Configure.pl option.
I am having the same problems a Mr Nagel. AFAIK I am buil
Claus Nagel wrote:
Hi,
an onwards with this slowly evolving error report on MS-platforms. Ron
gave a hint, but STDERR on Windows is just q{2>}, so running
PS D:\Src\rakudo> gdb .\parrot_install\bin\parrot.exe 2> error.txt
produces at least following error:
gdb.exe : warning: Query the
Claus Nagel wrote:
Hi,
I tried Bruce's suggestions (and failed miserably...)
Running parrot under gdb with:
(gdb) run src/gen/perl6.pbc --target=pir src/gen/core.pm
Starting program: D:\Src\rakudo/.\parrot_install\bin\parrot.exe
src/gen/perl6.pbc --target=pir src/gen/core.pm
[New Thread 4828.0
Ma Jinke wrote:
I put Rakudo from git under
C:\cygwin\home\admin\rakudo(cygwin:/home/admin/rakudo), It compiled nicely.
...
rakudo: "make test" is OK, but "make spectest" is FAILED!
When reporting a failure, as above, it would be helpful if you provided
specific error messages generated by by
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 si
A while back I across the web page: RFP: Parrot needs better smoke
reports (at url:
http://www.perlfoundation.org/parrot/index.cgi?rfp_parrot_needs_better_smoke_reports).
After reading the requirements for "Queryability" I decided to try to
write some web query forms and reports that fit those
So, since Rakudo's current grammar pretty much matches what STD.pm
has here, I'd prefer that we figure out how STD.pm is handling
empty statements and do that.
Thanks again!
Pm
As far as I can tell, STD.pm handles this problem in "token statement",
as shown below. If you modify the st
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 every
Moritz Lenz wrote:
Oops, forgot to attach patch. Now it's really there.
Your implementations of eval_lives_ok and eval_dies_ok seem
inconsistent. eval_lives_ok uses try and eval_dies_ok does not. The
two implementations may catch different types of exceptions. I am
proposing the patch b
11 matches
Mail list logo
