r24926 - docs/Perl6/Spec src/perl6 t/operators t/run

2009-01-15 Thread pugs-commits
Author: lwall Date: 2009-01-16 08:42:00 +0100 (Fri, 16 Jan 2009) New Revision: 24926 Modified: docs/Perl6/Spec/S03-operators.pod src/perl6/STD.pm t/operators/adverbial_modifiers.t t/run/02-dash-n.t t/run/03-dash-p.t Log: [STD] alignment with S03 on associativity noted by mtnviewmark

Re: Operator sleuthing...

2009-01-15 Thread Jon Lang
Mark Lentczner wrote: > STD has sym<;> as both an infix operator ( --> Sequencer), and as a > terminator. > ?? Which is it? Since I think most people think of it as a statement > terminator, I plan on leaving it off the chart. It is both. Examples where it is used as an infix operator include:

Operator sleuthing...

2009-01-15 Thread Mark Lentczner
I'm re-working my "Periodic Table of the Operators" chart to be up-to- date. I did the first major pass based on S03-operators. However, the last few days I've been plowing through STD.pm and have discovered that there some differences. Since STD.pm is considered more up to date, I'll be

Re: design of the Prelude (was Re: Rakudo leaving the Parrot nest)

2009-01-15 Thread Darren Duncan
Following some responses I've seen, I'll try to clarify my proposal. Basically its like this. A significant subset of Perl 6 native features, eg types and operators, native meaning they are declared and described in the Perl 6 Synopsis documents, have been implemented under Pugs by being writ

Re: design of the Prelude (was Re: Rakudo leaving the Parrot nest)

2009-01-15 Thread jason switzer
On Thu, Jan 15, 2009 at 8:59 PM, Jon Lang wrote: > OK, then. If I'm understanding this correctly, the problem being > raised has to do with deciding which language features to treat as > primitives and which ones to bootstrap from those primitives. The > difficulty is that different compilers p

Re: design of the Prelude (was Re: Rakudo leaving the Parrot nest)

2009-01-15 Thread Jon Lang
On Thu, Jan 15, 2009 at 6:45 PM, Jonathan Scott Duff wrote: > On Thu, Jan 15, 2009 at 8:31 PM, Jon Lang wrote: >> >> Forgive my ignorance, but what is a Prelude? >> >> -- >> Jonathan "Dataweaver" Lang > > The stuff you load (and execute) to bootstrap the language into utility on > each invocation

Re: design of the Prelude (was Re: Rakudo leaving the Parrot nest)

2009-01-15 Thread Darren Duncan
Jon Lang wrote: Forgive my ignorance, but what is a Prelude? The Prelude is a file written in Perl 6 that defines some Perl 6 built-ins. See http://perlcabal.org/svn/pugs/view/src/perl6/Prelude.pm for what AFAIK is the newest version. -- Darren Duncan

Re: design of the Prelude (was Re: Rakudo leaving the Parrot nest)

2009-01-15 Thread Jon Lang
Forgive my ignorance, but what is a Prelude? -- Jonathan "Dataweaver" Lang

Re: design of the Prelude (was Re: Rakudo leaving the Parrot nest)

2009-01-15 Thread Darren Duncan
Geoffrey Broadwell wrote: The problem with this method is that there are usually *several* ways to implement each feature in terms of some number of other features. The creators of the shared prelude are then stuck with the problem of deciding which of these to use. If their choices do not matc

Re: design of the Prelude (was Re: Rakudo leaving the Parrot nest)

2009-01-15 Thread Geoffrey Broadwell
On Thu, 2009-01-15 at 16:03 -0800, Darren Duncan wrote: > Patrick R. Michaud wrote (on p6c): > > On Thu, Jan 15, 2009 at 08:53:33AM +0100, Moritz Lenz wrote: > >> Another thing to keep in mind is that once we start to have a Perl 6 > >> prelude, we might decide to be nice neighbors and share it wit

design of the Prelude (was Re: Rakudo leaving the Parrot nest)

2009-01-15 Thread Darren Duncan
Patrick R. Michaud wrote (on p6c): On Thu, Jan 15, 2009 at 08:53:33AM +0100, Moritz Lenz wrote: Another thing to keep in mind is that once we start to have a Perl 6 prelude, we might decide to be nice neighbors and share it with other implementations, as far as that's practical. My guess is t