Re: RFC 128 (v1) Subroutines: Extend subroutine contexts to include name parameters and lazy arguments

2000-08-19 Thread Chaim Frenkel
Or the lack of a %rest? > "DC" == Damian Conway <[EMAIL PROTECTED]> writes: DC> * Label an argument such that there is no corresponding named DC> parameter. >> >> Could this be eased slightly? How about a %rest hash, if supplied >> in the prototype would absorb the unused named parameters

Re: RFC 128 (v1) Subroutines: Extend subroutine contexts to include name parameters and lazy arguments

2000-08-18 Thread Damian Conway
> Since there is a run-time component we could probably write a > proof-of-concept parser for some of this in perl5 now: > > use NamedParameters; This would certainly be an interesting and useful module. I encourage someone to create it. Of course, it couldn't (easily) include all

Re: RFC 128 (v1) Subroutines: Extend subroutine contexts to include name parameters and lazy arguments

2000-08-18 Thread Graham Barr
On Fri, Aug 18, 2000 at 06:04:55PM +1000, Damian Conway wrote: >> > An argument would be associated with a named parameter by >> > prefixing it with a standard Perl label (i.e. an identifier-colon >> > sequence). For example: >> > >> > @mapped = doublemap(args: @list,

Re: RFC 128 (v1) Subroutines: Extend subroutine contexts to include name parameters and lazy arguments

2000-08-18 Thread Damian Conway
> > An argument would be associated with a named parameter by > > prefixing it with a standard Perl label (i.e. an identifier-colon > > sequence). For example: > > > > @mapped = doublemap(args: @list, mapsub: ^a+^b); > > I persoanlly would prefer '=>' to be used here

Re: RFC 128 (v1) Subroutines: Extend subroutine contexts to include name parameters and lazy arguments

2000-08-18 Thread Hildo Biersma
> =head1 ABSTRACT > > This RFC proposes that subroutine argument context specifiers be > extended in several ways, including allowing parameters to be typed and > named, and that a syntax be provided for binding arguments to named > parameters. I agree with most, if not all, of this RFC. > =h

Re: RFC 128 (v1) Subroutines: Extend subroutine contexts to include name parameters and lazy arguments

2000-08-18 Thread Hildo Biersma
Chaim Frenkel wrote: > > DC> =head1 IMPLEMENTATION > > DC> Definitely S.E.P. > > What does that mean? Somebody Else's Problem. From one of the Douglas Adams novels.

Re: RFC 128 (v1) Subroutines: Extend subroutine contexts to include name parameters and lazy arguments

2000-08-17 Thread Damian Conway
> DC> * Label an argument such that there is no corresponding named > DC> parameter. > > Could this be eased slightly? How about a %rest hash, if supplied > in the prototype would absorb the unused named parameters? Yes, I've been rethinking that in light of my i

Re: RFC 128 (v1) Subroutines: Extend subroutine contexts to include name parameters and lazy arguments

2000-08-17 Thread Chaim Frenkel
> "DC" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: DC> * Label an argument such that there is no corresponding named DC> parameter. Could this be eased slightly? How about a %rest hash, if supplied in the prototype would absorb the unused named parameters? DC> =hea

RFC 128 (v1) Subroutines: Extend subroutine contexts to include name parameters and lazy arguments

2000-08-17 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Subroutines: Extend subroutine contexts to include name parameters and lazy arguments =head1 VERSION Maintainer: Damian Conway <[EMAIL PROTECTED]> Date: 17 August 2000 Version: 1 Mailing List: [EMAI