Re: Logo considerations - 3 logos needed
Perl 6 is more than just the test suite. It's a language specification, a reference parser, a test suite, and perhaps a reference setting implementation. All of the things about the language that are not tied to a particular implementation are part of "Perl 6". Rakudo is a particular implementation of Perl 6 using Parrot. While it is a separate project from both Perl 6 and Parrot, it is intimately tied to both, and I think its logo should reflect that. I don't see much point in having separate logos for "Rakudo on Parrot" and "Rakudo without Parrot". I mean, I suppose much of the frontend work could be ported to a different backend, but would that still be considered Rakudo? (Incidentally, the "Rakudo" name arose while I wasn't really paying attention to Parrot developments, and I missed its advent. So let me a-year-belatedly say that I find it a very nice coinage. Besides getting the camel and the idea of The Perl Way in there, and of course the "perl = paradise" implication is a nice touch, I like that if you squint at it sideways you can almost see the word "roku", which is Japanese for "six".)
Re: Logo considerations
Are we seeking a logo for Perl 6 in general or Rakudo in particular? It seems like the latter should be derived from the former, perhaps with the Parrot logo mixed in. On 3/24/09, Daniel Ruoso wrote: > Em Ter, 2009-03-24 às 09:01 -0300, Daniel Ruoso escreveu: >> A zombie cat? > > While I wasn't really serious about it... > > > > -- Sent from my mobile device Mark J. Reed
Re: Converting a Perl 5 "pseudo-continuation" to Perl 6
On Fri, Jan 2, 2009 at 9:06 PM, Geoffrey Broadwell wrote: > It does bring up a question, though. What if pid_file_handler() needed > to be broken into three or more pieces, thus containing multiple yield > statements? Does only the first one return a continuation object, which > can be called repeatedly to continue after each yield like this? IMO, that's not much better than not having the explicit continuation object in the first place. A true continuation should essentially be an immutable value object that can be repeatedly invoked to resume processing at the same point. >my &more_pid_stuff := pid_file_handler($pid_file); How does binding work with an rvalue like that? > Or does each yield produce a fresh new continuation object like this? That would definitely be my vote. -- Mark J. Reed
