On Tue, Jan 27, 2009 at 12:27:56AM +0100, Aristotle Pagaltzis wrote:
: * Aristotle Pagaltzis [2009-01-02 23:00]:
: > That way, you get this combination:
: >
: > sub pid_file_handler ( $filename ) {
: > # ... top half ...
: > yield;
: > # ... bottom half ...
: > }
:
Author: lwall
Date: 2009-01-27 01:44:28 +0100 (Tue, 27 Jan 2009)
New Revision: 25049
Modified:
docs/Perl6/Spec/S29-functions.pod
Log:
[S29] expand on use of * in orderings
sort, min, and max shouldn't have an optional positional before a slurpy
junctional functions take *...@array, not a single
Author: lwall
Date: 2009-01-27 01:08:23 +0100 (Tue, 27 Jan 2009)
New Revision: 25048
Modified:
docs/Perl6/Spec/S05-regex.pod
src/perl6/STD.pm
Log:
[STD, S05] converge spec and parse of character classes
Modified: docs/Perl6/Spec/S05-regex.pod
===
* Aristotle Pagaltzis [2009-01-02 23:00]:
> That way, you get this combination:
>
> sub pid_file_handler ( $filename ) {
> # ... top half ...
> yield;
> # ... bottom half ...
> }
>
> sub init_server {
> # ...
> my $write_pid = pid_file_handler( $
Author: lwall
Date: 2009-01-26 20:11:42 +0100 (Mon, 26 Jan 2009)
New Revision: 25044
Modified:
docs/Perl6/Spec/S02-bits.pod
Log:
[S02] clarify that .perl always represents an object as an item
Modified: docs/Perl6/Spec/S02-bits.pod
=
* Nicholas Clark [2009-01-24 15:00]:
> But personally I feel that the added conceptual complexity of
> having over-ridable regexps, and in particular .ltrim and
> .rtrim methods with over-ridable regexps is not worth it.
Yeah. I have come around to this view as well.
In programming, everythi
