And of course I find the bug someone else submitted *after* I send that message.
http://rt.perl.org/rt3/Public/Bug/Display.html?id=68744
Nothing new to see here, move along...
On Thu, Sep 3, 2009 at 10:51 PM, Mark J. Reed wrote:
> Possibly a known bug, but Rakudo (at least on OS X) is treating
Possibly a known bug, but Rakudo (at least on OS X) is treating REPL
input as Latin-1, even though it treats script code and command-line
code properly as UTF-8 (which matches my locale settings):
$ ./perl6 -e 'for «Hello world!» { .say }'
Hello
world!
$ ./perl6 > for «Hello world!» { .say }
Stat
parrot.org admins are on this; Hopefully will be done today.
On Thu, Sep 3, 2009 at 10:52 AM, yary wrote:
> I'm running one of the buildslave smoke testing machines for parrot,
> and noticed that mine & the other buildslaves are failing. Seems to be
> due to the clients' vigilant checking of SSL c
I'm running one of the buildslave smoke testing machines for parrot,
and noticed that mine & the other buildslaves are failing. Seems to be
due to the clients' vigilant checking of SSL certificates-
http://buildbot.eigenstate.net:8040/OpenBSD-trunk-builder/builds/14/step-svn/0
says:
svn: PROPFIND
# New Ticket Created by Solomon Foster
# Please include the string: [perl #68960]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68960 >
colomon: rakudo: say "hello"; say 1 / 0; say "goodbye"
p6eval: rakudo c9a930: OUTPUT«h
# New Ticket Created by Solomon Foster
# Please include the string: [perl #68958]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68958 >
colomon: rakudo: say Rat.new.Str
p6eval: rakudo c9a930: OUTPUT«Null PMC access in find
