cvsuser 04/02/25 13:32:05
Modified: ops object.ops Log: Update the docs in line with PDD15 Revision Changes Path 1.29 +20 -9 parrot/ops/object.ops Index: object.ops =================================================================== RCS file: /cvs/public/parrot/ops/object.ops,v retrieving revision 1.28 retrieving revision 1.29 diff -u -w -r1.28 -r1.29 --- object.ops 25 Feb 2004 20:49:43 -0000 1.28 +++ object.ops 25 Feb 2004 21:32:05 -0000 1.29 @@ -20,24 +20,35 @@ =item B<callmethod>() -Call a method on an object as per Parrot's calling conventions. We assume -that all the registers are properly set up. +=item B<callmethod>(in STR) -All calls assume P2 = object, S0 = method. +Call a method on an object. If a method name is provided, we find +the PMC for the named method and put it into the sub/method slot. +If no name is provided, then we assume that the method PMC and +method name are already in their proper places. We assume that +all other registers are correctly set up, as per the Parrot +calling conventions. =cut -=item B<callmethodcc> +=item B<callmethodcc>() -Take the continuation for the next instruction, put it in P1, then call the -method as per the calling conventions. +=item B<callmethodcc>(in STR) + +Make a method call, automatically generating a return continuation. If +a method name is passed in we look up the method PMC for the object +and put it in the method slot. If a method name isn't provided then we +assume that things are already properly set up. Note that the return +continuation is placed in P1. =cut -=item B<tailcallmeth> +=item B<tailcallmethod> + +=item B<tailcallmethod>(in STR) -Restore the continuation in P1 then call the method as per the calling -conventions. +Make a tailcall to method $1. If no method name is given, we assume +everything is already set up properly. =cut
