Re: Method name and/or line number available from withinForte?

Question

To my knowledge there is no such capability with forte, and for sure it
would be nice. Short
of storing all that metadata at runtime, a compile-time substitution such
as is done with
most C preprocessors would work as well.
However, I believe the solution you've identified falls short in a deployed
fashion - I think
all that method name/line number stuff is only available from the workshop...
-J
At 02:54 PM 10/27/98 -0600, [email protected] wrote:
I'm sure this question has been asked many times, but I don't know that I've
ever heard the answer. Is there any way from Forte to access the method
name of the currently executing method? What about the current line number?
I'm sure you all know what I'm getting at by now -- when raising your own
custom exceptions or logging messages we'd like to be able to not hard-code
method names and line numbers into them. I know these are available with
log flags so this information is stored somewhere -- is there an API to
access it on an agent, the task, or the environment? The only way I can
think of doing this (which is not-so-elegant) is to force a Forte exception
to be raised (like access a method on a null TextData or something), then
immediately catch it and extract the method and line number from it. Is
there a more elegant way?
-J.C.
J.C. Hamlin, Senior Consultant, Forte National Practice
Born Information Services Group, Wayzata, MN
Ph: [phone] Ph2: [phone] FAX: [phone]
<[email protected]> <[email protected]>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>**************************************
John L. Jamison
Vice President and Chief Technology Officer
Sage IT Partners, Inc.
415 392 7243 x 306
[email protected]
The Leaders in Internet Enabled Business Change
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

Method task.TraceBack () returns a string suitable for shoving on the error
stack, and representing a call trace. The method
method TomW_RaiseException.RaiseException
begin
ge : GenericException = New ();
ge.SetWithParams (SP_ER_USER, task.TraceBack ());
task.ErrorMgr.AddError (ge);
Raise ge;
end method;
produces the following when called from the display method of the window in
which it is embedded.
USER ERROR:
Traceback:
TomW_RaiseException.RaiseException at line 2
TomW_RaiseException.Display at line 4
TomW_RaiseException. at offset 13
C++ Method(s)
UserApp.Run at offset 96
Class: qqsp_Exception
Last TOOL statement: method TomW_RaiseException.RaiseException, line 3
Error Time: Wed Oct 28 08:28:34
Exception occurred (locally) on partition "TomW_Test_CL0_Client",
(partitionId = AA6475E0-3DD2-11D2-B582-04228BFFAA77:0x117f:0x6,
taskId =
[AA6475E0-3DD2-11D2-B582-04228BFFAA77:0x117f:0x6.34]) in application
"FTLaunch_cl0", pid 195 on node SPNMXSHOP7 in environment SFDEVL.
I suppose that a sufficiently determined person could parse the results of
TraceBack () and extract the
method and line from it. But I know of no method that explicitly returns
the name of the calling method.
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>