Re: RFC 174 (v1) Parse C<func($obj, @args)> as C<func $obj (@args)>
[email protected] (Tom Christiansen) Wed, 30 Aug 2000 17:41:56 -0600
| Newsgroups | perl.perl6.language.subs |
|---|---|
| Message-ID | <2788.967678916@chthon> |
>Doesn't this move compile time work into run-time? If you can't know till run-time what function to call, then yes. In which case Perl's dispatch will start being as slow as Python's--and for the same underlying reason. Infinite flexibility means infinite slowness. Oh, and look at this crud: >>>>>>>>>>>> BEGIN MISPLACED OVERQUOTED OVERQUOTED TEXT <<<<<<<<<<<<<<<<<<<<<<<<< +--------------------------------------------------------------------------------+ | >>>>>> "PRL" == Perl6 RFC Librarian <[email protected]> writes: | | | | >PRL> This should be made to work correctly. The following order of function | | >PRL> parsing should apply to Perl 6: | | | | >PRL> 1. The current package should be checked for a function | | >PRL> by that name (including any imported ones), consistent | | >PRL> with current behavior. | | | | >PRL> 2. Argument 1 should be checked to see if it is a valid | | >PRL> object reference. If so, the method should be checked | | >PRL> for existence as a member. | | | | >PRL> 3. AUTOLOAD should be called. | | | | >PRL> The only new step here is step #2. Notice that this does NOT override | | >PRL> current-package functions. Only if a function is not found in the | | >PRL> current package is the translation attempted. | | | | >-- | | >Chaim Frenkel Nonlinear Knowledge, Inc. | | >[email protected] +1-718-236-0183 | +--------------------------------------------------------------------------------+ >>>>>>>>>>>> END MISPLACED OVERQUOTED OVERQUOTED TEXT <<<<<<<<<<<<<<<<<<<<<<<<< This isn't jeopardy. Blech. You've done this about five times today. Your mailer is screwed. --tom