Graham Barr wrote:
>
> I would add to that, that as long as the addition of this does not effect
> the performance of calling the methods that want the "relaxed perl5-ish"
> semantics.
>
> Graham.
The IMPLEMENTATION of the rfc97 working document (unfortuneately
not web accessible, I may change that) now reads in part:
Perhaps the method is first looked up by name, and then further
dispatch is done if needed. This would exempt methods using "relaxed
perl5-ish semantics" from any additional processing overhead.
--
David Nicol 816.235.1187 [EMAIL PROTECTED]
Useless use of a void in constant context
- Re: RFC 97 (v1) prototype-based method overloading Ask Bjoern Hansen
- Re: RFC 97 (v1) prototype-based method overloading Chaim Frenkel
- Re: RFC 97 (v1) prototype-based method overload... Piers Cawley
- Re: RFC 97 (v1) prototype-based method over... Chaim Frenkel
- Re: RFC 97 (v1) prototype-based method ... Peter Buckingham
- Re: RFC 97 (v1) prototype-based me... Nick Ing-Simmons
- Re: RFC 97 (v1) prototype-based method overload... Damian Conway
- Re: RFC 97 (v1) prototype-based method over... Piers Cawley
- Re: RFC 97 (v1) prototype-based method overloading Nick Ing-Simmons
- Re: RFC 97 (v1) prototype-based method overloading Graham Barr
- RE: RFC 97 (v1) prototype-based method overload... David L. Nicol
- RE: RFC 97 (v1) prototype-based method overloading Evan Howarth
- Re: RFC 97 (v1) prototype-based method overloading Chaim Frenkel
- Re: RFC 97 (v1) prototype-based method overload... Piers Cawley
