Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-21 Thread Michael G Schwern
CAPS LOCK KEY STUCK STOP CANNOT PROGRAM PERL REVERTING TO BASIC STOP SEND HELP QUICK STOP -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse When faced with desperate circumstances, we

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-20 Thread Ilya Zakharevich
On Tue, Sep 19, 2000 at 08:05:50PM -0700, Nathan Wiger wrote: $_ is not ALLCAPS. @EXPORT_OK should die (see RFC 233). @ISA is on its way to its grave already, see Cuse base. Yeah, but you're still just sidestepping my point. Your position seems poised on the hope that no more special

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-19 Thread Ilya Zakharevich
== No special UPPERCASE_NAME subroutines Whoa! What about ALLCAPS variables? Should we axe all of them as well? They're the exact same idea. == What ALLCAPS

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-19 Thread Nathan Wiger
Ilya Zakharevich wrote: == No special UPPERCASE_NAME subroutines Whoa! What about ALLCAPS variables? Should we axe all of them as well? They're the exact same idea.

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-19 Thread Ilya Zakharevich
On Tue, Sep 19, 2000 at 04:22:31PM -0700, Nathan Wiger wrote: What ALLCAPS variables? Well, @ARGV comes to mind. I see, and @INC, %INC, %ENV, %SIG. Maybe we should provide a special namespace for these as well, besides main::? This is a nice possible solution. There may be many others

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-19 Thread Nathan Wiger
Ilya Zakharevich wrote: On the other hand, there are only 5 names, not hundreds of them, and they do not "get in the way", as ADD would do (prohibiting a method named ADD). So letting them be may be also a solution... Uhhh, I think you should check the Camel. These variables certainly do

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-19 Thread Ilya Zakharevich
On Tue, Sep 19, 2000 at 04:50:04PM -0700, Nathan Wiger wrote: Ilya Zakharevich wrote: On the other hand, there are only 5 names, not hundreds of them, and they do not "get in the way", as ADD would do (prohibiting a method named ADD). So letting them be may be also a solution...

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-19 Thread Nathan Wiger
Ilya Zakharevich wrote: The presence of a method STORE is visible outside of the module, and may be required* if the module follows some published (non-Perl) API. Variables are of different ilk. I think you're overlooking they can both be equally visible: $Foo::DEBUG = 1;

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-19 Thread Ilya Zakharevich
On Tue, Sep 19, 2000 at 06:39:49PM -0700, Nathan Wiger wrote: The presence of a method STORE is visible outside of the module, and may be required* if the module follows some published (non-Perl) API. Variables are of different ilk. I think you're overlooking they can both be equally

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-19 Thread Nathan Wiger
Ilya Zakharevich wrote: $_ is not ALLCAPS. @EXPORT_OK should die (see RFC 233). @ISA is on its way to its grave already, see Cuse base. Yeah, but you're still just sidestepping my point. Your position seems poised on the hope that no more special variables get introduced, or that some of

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-17 Thread Bart Lateur
On 16 Sep 2000 08:08:05 -, Perl6 RFC Librarian wrote: If some special action handler needs to be registered, this should be done not by using a special name, but by a pragma. use tie STORE = sub { ... }; not sub STORE { ... } Hmmm... this sounds like a less efficient approach. I

Re: RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-16 Thread Nathan Wiger
No special UPPERCASE_NAME subroutines Whoa! What about ALLCAPS variables? Should we axe all of them as well? They're the exact same idea. If some special action handler needs to be registered, this should be done not by using a special name, but by a pragma. use tie STORE = sub { ... };

RFC 243 (v1) No special UPPERCASE_NAME subroutines

2000-09-16 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE No special UPPERCASE_NAME subroutines =head1 VERSION Maintainer: Ilya Zakharevich [EMAIL PROTECTED] Date: 15 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 243 Version: 1 Status: Developing