> I can't answer your question, but I would like to know what your
> application for this functionality would be.
I stuff my apps to the gills with error checking. In this particular
case, I'm talking to an Oracle data source for error logging. I'd love
to be able to do the following:
<pseudo>
on ThisGlobalHandler()
...
if bError then
oErrLog.mLog( the currentHandler, strDescr, intSeverity, bActionReq
)
-- or better yet, this:
oErrLog.mLog( callStack[ callStack.count ], strDescr, intSeverity,
bActionReq )
end if
end
</pseudo>
Right now, I'm having to use:
oErrLog.mLog( "ThisGlobalHandler", strErr, etc ) <-- I DON'T LIKE THIS
Something like 'the currentHandler' would be really handy for this type
of error-logging scenario, and as Christopher Watson suggested, 'the
callStack' would be even better. Director displays this into in the
debugger; why not provide access to it from Lingo?
And to finally get around to my point: I'd like to use
scriptObj.handlers() to build a COM-esque IUnknown::QueryInterface, but
without a smart way of knowing which handler is curently executing,
there's not much sense in it.
Rob
/*********************************
* Rob Wingate, Software Human *
* http://www.vingage.com *
* mailto:[EMAIL PROTECTED] *
*********************************/
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
