Re: RFC 187 (v1) Objects : Mandatory and enhanced second argument to Cbless
On 1 Sep 2000 20:59:10 -, Perl6 RFC Librarian wrote: When omitted, the second argument to Cbless currently defaults to the name of the package from which the call is made. The word "from" doesn't look like it's been used 100% correctly. "Being called from" suggests that it's the name af the caller package that gets used. Instead, it's the package in which the method is defined. -- Bart.
Re: RFC 187 (v1) Objects : Mandatory and enhanced second argument to Cbless
On 1 Sep 2000 20:59:10 -, Perl6 RFC Librarian wrote: This RFC proposes that the second argument to Cbless be made mandatory, and that its semantics be enhanced slightly to cover a common, ugly, and frequently buggy usage. Ooh, how about this alternative. There must be an RFC making the current implementation of object methods safer, by passing the object or class not the first item in the parameter list, but available either through a vairable ($SELF, $ME, ...) or though a function similar in nature to caller(): self(). How about if we defaulted the still optional second parameter to bless, into the class name of this object or class, i.e. self(). -- Bart.
Re: RFC 187 (v1) Objects : Mandatory and enhanced second argument to Cbless
"Perl6" == Perl6 RFC Librarian [EMAIL PROTECTED] writes: Perl6 This RFC proposes that the second argument to Cbless be made Perl6 mandatory, and that its semantics be enhanced slightly to cover a Perl6 common, ugly, and frequently buggy usage. Yes! -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 [EMAIL PROTECTED] URL:http://www.stonehenge.com/merlyn/ Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
