On 1/15/06, Alfred Van Hoek <vanhoek at mac dot com> wrote:
>
> On Jan 15, 2006, at 2:11 PM, Alexander Traud wrote:
>
> >> happy that these function pointers are not destroyed magically.
> >
> > Yes, but several strings on the heap are something else than a function
> > pointer. Yes, a REALbasic function pointer could move but we have
> > concepts
> > like handles or similar for something like that. I see no reason why
> > the
> > *NAME of a parameter* is hold on the heap.
> >
>
> Not that I don't agree with you. Dynamic access evaluates the complete
> signature to allow screening for overloaded methods, which can contain
> optional parameters, contrary to RB's plugin API's. Plugin API's use
> "Direct Access" entry points, which screen for the method name only.
> Plugin API function pointers are persistent following lazily creation.
> In Dynamic Access NAME and DEFAULT value, or OPTIONAL on the heap may
> be essential, but this is based on a gut feeling only.
I think there's a misunderstanding on what REALLoadObjectMethod does.
It simply scans the class of the object passed in for a method
matching the signature. You are responsible for specifying all the
parameters, including optional ones, and you are responsible for
passing all parameters in. The returned result is simply the same
function pointer that REALbasic calls through the vtable. There is no
need to unlock anything.
If there is a leak, that's a bug. Please file a report with an
included example plugin and project.
Thanks,
Jon
--
Jonathan Johnson
REAL Software, Inc.
REAL World 2006, The REALbasic User's Conference
<http://www.realsoftware.com/realworld>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|