BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20090513T00Z
DTEND:20090513T03Z
DTSTAMP:20090507T205457Z
ORGANIZER;CN=Art Schmidt:mailto:fri...@gmail.com
UID:sba7al7vh82ld3ccni8rttu...@google.com
ATTENDEE;C
more organized in the future, but for now this will work :-)
--
fREW Schmidt
http://blog.afoolishmanifesto.com
> > And should I
> > just mail patches to rakudo...@perl.org?
>
> In general if you find a bug: yes.
> In this case not, because it's a known limitation.
Where do I mail the patches for the tests?
--
-fREW
Hi!
I'd like to get started adding these:
is capitalize(:string($a)), "Pugs Is Cool!", "capitalize works with named
arg"
rakudo and pugs both fail this test. Should I add it anyway? And should I
just mail patches to rakudo...@perl.org? Or should this technically be
pugs?
--
-fREW
> Since the tests are all written in Perl 6, you have to learn at least a
> bit of the language.
I figured that; I just wanted to start off with perl6 before I did
anything in PIR.
> In the pugs repo there's a file in t/TASKS that contains a list of
> things to be done - maybe you can start there
Hello friends!
I just recently read Ovid's post on use Perl about how we can help by
fixing PUGS tests. I was a little clear on what he meant and I am a
little anxious to do something. I checked out the code for parrot
already and I am getting the pugs code while I write this. Anyone
have any i
