Re: RFC 244 (v1) Method calls should not suffer from the action on a distance

2000-09-26 Thread Ilya Zakharevich
On Mon, Sep 25, 2000 at 09:10:49PM -0700, Nathan Wiger wrote: >if ( want->{count} > 2 ) { return $one, $two } > > Will that be interpreted as: > >'want'->{count} >want()->{count} > > To be consistent, it should mean the first one. That is, the infix > operator -> should always autoq

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 C. > > Yeah, but you're still just sidestepping my point. Your position seems > poised on the hope that no more special vari

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 equ

Re: RFC 244 (v1) Method calls should not suffer from the action on a distance

2000-09-19 Thread Ilya Zakharevich
On Tue, Sep 19, 2000 at 04:52:12PM -0700, Nathan Wiger wrote: > Ok, you should clarify this. You're not suggesting that indirect object > syntax be removed. You're suggesting that it should not accept > barewords. These are two separate things. Agreed. I realized the ambiguity only after I poste

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 l

Re: RFC 244 (v1) Method calls should not suffer from the action on a distance

2000-09-19 Thread Ilya Zakharevich
On Tue, Sep 19, 2000 at 04:26:47PM -0700, Nathan Wiger wrote: > > $IO::STDERR->print @stuff; > > print $IO::STDERR @stuff; > > Ok, something here is extreme confused. Is not the second form an > instance of indirect object syntax? It is not with a bareword at the second place, so is not caus

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 ot

Re: RFC 244 (v1) Method calls should not suffer from the action on a distance

2000-09-19 Thread Ilya Zakharevich
== Please show me how to write: print STDERR @stuff; without it, while keeping it a method of the STDERR filehandle, and without requiring ->. == Why not use ->?

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 variables

Re: RFC 242 (v1) No overloading of f($arg) basing on ref($arg)

2000-09-19 Thread Ilya Zakharevich
a) I do not subscribe to Perl6 lists, so please consider including me on the Cc lines; b) == * From: Nathan Wiger > There are several proposals to switch the meaning of C basing on > the whether $arg is an array reference

Re: RFC 232 (v1) Replace AUTOLOAD by a more flexible mechanism

2000-09-15 Thread Ilya Zakharevich
On Fri, Sep 15, 2000 at 03:11:47PM -0600, Nathan Torkington wrote: > Perl6 RFC Librarian writes: > > This RFC proposes two-stage autoloading: one stage may be registered > > to act when the symbol is encountered at compile time, the other > > when the subroutine is called. Autoloading on the seco

Re: Proposal for \v and \V, the small- and large- cut regex opera tors.

2000-08-10 Thread Ilya Zakharevich
On Thu, Aug 10, 2000 at 11:12:28AM +0200, Johan Vromans wrote: > Of course, we need group names (trivial), and group temporaries. > I needed the latter to define a generic pattern to match quoted strings: > you need to store the starting quote somewhere to find the ending quote, > but I didn't wan

Re: Proposal for \v and \V, the small- and large- cut regex opera tors.

2000-08-10 Thread Ilya Zakharevich
On Thu, Aug 10, 2000 at 10:16:12AM +0200, Johan Vromans wrote: > > "(" (.) group(1, [[ 'a' .. 'z' ]] (*) [3,5] ) (.) ")" > > > > here (.) is the ASCII substitution for the UNICODE "REx concatenate" > > char, similarly for [[. ]] and (*). (The chars may be borrowed from > > the math repertoire.