use v5 Support

I want to pose the same question for clarification that I asked #perl6: S01 says that perl5 code will be supported via "use v5". Can someone confirm that embedded perl5 code is still required of any valid implementation? If so, how will XS code be supported? Will the namespace between v5 code and

Re: Logo considerations - 3 logos needed

On Wed, Mar 25, 2009 at 6:06 PM, Larry Wall wrote: > > http://www.wall.org/~larry/cameliafav.ico > > out to be necessary. Hand-crafted anti-aliasing is your friend. :) > Larry > firefox at 3025%: cameliafav.ico all blown up. [groan] http://feat

Re: Logo considerations - 3 logos needed

On Wed, Mar 25, 2009 at 03:43:47PM -0400, Guy Hulbert wrote: : On Wed, 2009-25-03 at 09:39 -0700, Larry Wall wrote: : > On Wed, Mar 25, 2009 at 08:54:34AM -0400, Guy Hulbert wrote: : > : On Wed, 2009-25-03 at 22:45 +1100, Timothy S. Nelson wrote: : > : > Additionally, while you recommended

Re: .map/.reduce with larger arity

Leon Timmermans wrote: > I would propose there to be one difference between for an map: map > should bind its arguments read-only, for should bind them read-write. > That would make at least one bad practice an error. That sounds very impractical, because the ro/rw distinction is part of the sign

Re: .map/.reduce with larger arity

Leon Timmermans wrote: > I would propose there to be one difference between for an map: map > should bind its arguments read-only, for should bind them read-write. > That would make at least one bad practice an error. That sounds very impractical, because the ro/rw distinction is part of the sign

Re: .map/.reduce with larger arity

On Wed, Mar 25, 2009 at 6:20 PM, Leon Timmermans wrote: > I would propose there to be one difference between for an map: map > should bind its arguments read-only, for should bind them read-write. > That would make at least one bad practice an error. Why is r/w map a bad practice if r/w for is no

Re: .map/.reduce with larger arity

On Tue, Mar 10, 2009 at 12:09 AM, Larry Wall wrote: > > Yes, the only difference between C and C is that you can > only use C at the start of a statement.  But we're more liberal > about where statements are expected in Perl 6, so you can say things > like: > >    my @results = do for @list -> $x

Re: Logo considerations - 3 logos needed

On Wed, 2009-25-03 at 09:39 -0700, Larry Wall wrote: > On Wed, Mar 25, 2009 at 08:54:34AM -0400, Guy Hulbert wrote: > : On Wed, 2009-25-03 at 22:45 +1100, Timothy S. Nelson wrote: > : > Additionally, while you recommended Camelia for Rakudo, my > : > understanding was that Larry was recomm

Re: decision operator

On Wed, Mar 25, 2009 at 12:25:59AM +0100, Moritz Lenz wrote: : Ruud H.G. van Tol wrote: : > I wonder if there is place for a "decision operator". : : This looks like a perfect place for a (possibly user defined) operator : with an attribute, something like : : 1 ~~ 0 :dop(7) To me it looks more l

Re: Logo considerations - 3 logos needed

On Wed, Mar 25, 2009 at 08:54:34AM -0400, Guy Hulbert wrote: : On Wed, 2009-25-03 at 22:45 +1100, Timothy S. Nelson wrote: : > Additionally, while you recommended Camelia for Rakudo, my : > understanding was that Larry was recommending it for Perl 6 rather than : > Rakudo. This is correc

r25999 - docs/Perl6/Spec

Author: ruoso Date: 2009-03-25 18:49:05 +0100 (Wed, 25 Mar 2009) New Revision: 25999 Modified: docs/Perl6/Spec/S11-modules.pod Log: [spec/S11] :DEFAULT is default in "is export" Modified: docs/Perl6/Spec/S11-modules.pod === --- d

Re: Logo considerations - 3 logos needed

On Wed, 2009-25-03 at 09:59 -0500, Patrick R. Michaud wrote: > On Wed, Mar 25, 2009 at 10:36:56AM -0400, Mark J. Reed wrote: > > 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 th

Re: Logo considerations - 3 logos needed

Not speaking for Larry but ... On Wed, 2009-25-03 at 22:45 +1100, Timothy S. Nelson wrote: > My understanding was that Rakudo only runs on top of Parrot. Either > way, I don't see why we need a logo for Parrot + Rakudo, any more than we need I think it's a logo for Rakudo = Parrot + Per

Re: Logo considerations - 3 logos needed

On Wed, Mar 25, 2009 at 10:36:56AM -0400, Mark J. Reed wrote: > 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

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 implementat

Re: Logo considerations - 3 logos needed

> > > But IMHO there is a need for three logos: > > 1. Combined Parrot + Rakudo > > (Parrot with speech bubbles in favicon halo)++ > > > 2. Rakudo > > Camelia++ > > > 3. "Perl6 = the test suite" > > The current plan is that Perl6 will not have a single implementation but > that the test suite is

Re: Logo considerations - 3 logos needed

I like the "Camelia" it's colourful, fun - it even has an embedded, sideways reference to a "Camel". But IMHO there is a need for three logos: 1. Combined Parrot + Rakudo I like the suggestion of having cartoon "speech bubbles" around the Parrot that contain favicons of the language icons (e.g.,

butterfly and Perl

re the logo: http://www.norfolkbirding.com/Pearl-Bordered-Fritillary.jpg

Re: Logo considerations

On Wed, 2009-25-03 at 10:45 +1100, Timothy S. Nelson wrote: > In response to those asking for a professional designer, I'd like to > see us go around a few more times here, and see if we can't come up with at > least a good concept that could hopefully be used/stylised by a real graphic

Re: Logo considerations - 3 logos needed

On Wed, 25 Mar 2009, Nigel Hamilton wrote: I like the "Camelia" it's colourful, fun - it even has an embedded, sideways reference to a "Camel". But IMHO there is a need for three logos: I'm not so sure 1. Combined Parrot + Rakudo [snip] 2. Rakudo My understanding was that Raku

Re: Logo considerations

On Tuesday, 24. March 2009 05:47:12 Darren Duncan wrote: > If you're going for sciencey or mathey illustrations, then I think its > important to include something that speaks quantum physics in there, since > quantum superpositions aka Junctions are one of the big central user > features that Perl