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 m
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 C.
>
> Yeah, but you're still just sidestepping my point. Your position seems
> poised on the hope that no more special vari
Ilya Zakharevich wrote:
>
> $_ is not ALLCAPS. @EXPORT_OK should die (see RFC 233). @ISA is on
> its way to its grave already, see C.
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 the exi
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 equ
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;
Foo::S
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..
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 d
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 ot
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.
> ===
==
> 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 variables
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
> 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 { .
12 matches
Mail list logo
