> We also have to have a way to fetch the method PMC for a named method > for later use, which is where the interesting bits come in. > > This is required for a number of reasons, including Python, so we > have to have it. The question is... *When* is the name resolved? That > is, if we do: > > findmethod P4, Pobject, "methodname" > > does the method PMC that gets stuck in P4 represent the method > "methodname" for the object *at that point in time* or does it > represent the method *at the time it is invoked*? That is, do we > defer actual lookup until invocation, or do we resolve at method find > time? > > This has some implications for when methods are overridden and > namespaces swapped in and out, so it's (unfortunately) not an > academic exercise. > --
is it too much trouble to implement both, and give the HLLs a choice of which they call? would 'findmethod_sooner' and 'findmethod_later' be too difficult to implement, or too large to add to the core ops? what do you lose by offering both, as opposed to one or the other? i wish i had more answers than questions... --jerry *no longer just a lurker* ************************************************************************** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
