Re: S26 - The Next Generation

2009-09-07 Thread Ruud H.G. van Tol
Jon Lang wrote: An unrelated possibility would be to allow empty A<> tags in a declarator block, with 'A<>' being replaced with the name of the declarator to which the block is attached: And then I think: A<_> -- Ruud (indoctrinated)

Re: S26 - The Next Generation

2009-09-07 Thread Jon Lang
Damian Conway wrote: > Jon Lang kept his promise: > >> I promised some further thoughts; here they are: > > Much appreciated. You're welcome. >> As written, declarator aliasing attaches the alias to a piece of code, >> and draws both the name and the alias from that.  What about using a >> specia

Re: S26 - The Next Generation

2009-09-07 Thread Jon Lang
Damian Conway wrote: > Raiph elucidated: >> I was thinking it would be possible to reference (compiler) variables >> representing eg. the name and sig of a block being parsed, or a block >> or declaration which has just been parsed, or which is just about to be >> parsed, and that simply referencin

Re: S26 - The Next Generation

2009-09-07 Thread Damian Conway
Jon Lang kept his promise: > I promised some further thoughts; here they are: Much appreciated. > As written, declarator aliasing attaches the alias to a piece of code, > and draws both the name and the alias from that.  What about using a > special case of the declarator block for this?  That

Re: S26 - The Next Generation

2009-09-07 Thread Damian Conway
Raiph elucidated: > Hmm. I was thinking Pod would be parsed by a P6/PGE grammar, one that > could be relatively easily edited/extended to suit another context, because, > I thought, it could then be made available as a stock --doc subsystem that > all PCT based languages get more or less for free.

program vs module (was Re: r28199 ...)

2009-09-07 Thread Darren Duncan
pugs-comm...@feather.perl6.nl wrote: +All package bodies (including module and class bodies) execute at the +normal execution time of the code in which they are embedded. For normal +mainline code, this is the normal flow of execution; if this is too late +to initialize something in the package

r28201 - docs/Perl6/Spec

2009-09-07 Thread pugs-commits
Author: lwall Date: 2009-09-07 20:32:55 +0200 (Mon, 07 Sep 2009) New Revision: 28201 Modified: docs/Perl6/Spec/S06-routines.pod Log: [S06] remove the slightly non-sensical 'use GLOBAL' in favor of 'defines' Modified: docs/Perl6/Spec/S06-routines.pod ===

r28199 - docs/Perl6/Spec

2009-09-07 Thread pugs-commits
Author: lwall Date: 2009-09-07 19:53:06 +0200 (Mon, 07 Sep 2009) New Revision: 28199 Modified: docs/Perl6/Spec/S04-control.pod docs/Perl6/Spec/S10-packages.pod docs/Perl6/Spec/S12-objects.pod Log: [S10] specify time of execution of package blocks and module (non)mainline code [S12] give e

Re: r28196 - docs/Perl6/Spec

2009-09-07 Thread Moritz Lenz
yary wrote: [ a lot of good things that make lot of sense ] Your complaints and review by TimToady and pmichaud on #perl6 convinced me that this is not a good idea after all, see http://irclog.perlgeek.de/perl6/2009-09-07#i_1475421 Cheers, Moritz

r28197 - docs/Perl6/Spec

2009-09-07 Thread pugs-commits
Author: moritz Date: 2009-09-07 19:30:17 +0200 (Mon, 07 Sep 2009) New Revision: 28197 Modified: docs/Perl6/Spec/S12-objects.pod Log: [S12] undo '...' semantics in class bodies. Now only a single ... term in the classes marks that class as a forward declaration, making it a declaration. Modifi

Re: r28196 - docs/Perl6/Spec

2009-09-07 Thread Patrick R. Michaud
On Mon, Sep 07, 2009 at 09:56:51AM -0700, yary wrote: > I just saw the intent for this in the " split up compilation of the > setting" thread- that it is useful to: > >Enable a "class stub" syntax that allows us to declare a given symbol > > as being a valid class without having to declare the body

Re: r28196 - docs/Perl6/Spec

2009-09-07 Thread yary
I just saw the intent for this in the " split up compilation of the setting" thread- that it is useful to: >Enable a "class stub" syntax that allows us to declare a given symbol > as being a valid class without having to declare the body of the > class at that time. For example: > > class Rat

Re: r28196 - docs/Perl6/Spec

2009-09-07 Thread yary
This spec subtly alters the meaning of "...". Whereas "yada" used to mean "this is not yet implemented, complain if executed" it now adds "but don't complain if it is a class fully implemented elsewhere". Allowing two implementations of a class iff one of them has a yada opens up maintenance issue