> With the proliferation of special subroutine names (BEGIN, END, INIT, > CHECK, etc.) the all capital subroutine names available to the > programmer has steadily shrunk. Rather than stealing subroutines from > the programmer, we should create a space just for Perl. > > sub *BEGIN { > # do compile-time stuff > # Perl-special > } I think this is a very valid point, but I don't think a special character should be chewed up for this. In particular, I really don't see typeglobs going away (they do some things you can't do otherwise). Besides, subs already have a magic character - the word "sub". Maybe just a convention like a leading underscore or two + CAPS? sub _TIESCALAR {} sub _FETCH {} sub _STORE {} sub _DESTROY {} -Nate
- Re: RFC 59 (v1) Proposal to utilize C<... Jonathan Scott Duff
- Re: RFC 59 (v1) Proposal to utilize C<... Bart Lateur
- Re: RFC 59 (v1) Proposal to utilize C... Peter Scott
- Re: RFC 59 (v1) Proposal to util... Piers Cawley
- Re: RFC 59 (v1) Proposal to ... Jonathan Scott Duff
- Re: RFC 59 (v1) Proposal to ... John Porter
- Re: RFC 59 (v1) Proposal to ... Peter Scott
- Re: RFC 59 (v1) Proposal to ... Piers Cawley
- Re: RFC 59 (v1) Proposal to util... Bart Lateur
- Re: RFC 59 (v1) Proposal to ... Bart Lateur
- Re: RFC 59 (v1) Proposal to utilize C<*> as the ... Nathan Wiger
- Re: RFC 59 (v1) Proposal to utilize C<*> as... Peter Scott
- Re: RFC 59 (v1) Proposal to utilize C<*>... Nathan Wiger
- Re: RFC 59 (v1) Proposal to utilize C<*> as the ... Piers Cawley
- Re: RFC 59 (v1) Proposal to utilize C<*> as... Jonathan Scott Duff
- Re: RFC 59 (v1) Proposal to utilize C<*> as the ... skud
- RE: RFC 59 (v1) Proposal to utilize C<*> as the ... Brust, Corwin