[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: caller function? function to get dependencies?
From: |
Andreas Romeyke |
Subject: |
Re: caller function? function to get dependencies? |
Date: |
Fri, 20 Apr 2007 11:25:17 +0200 |
User-agent: |
Icedove 1.5.0.10 (X11/20070329) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello John,
John W. Eaton wrote:
> Starting with Octave 2.9.6 it is possible to get the call stack in
> C++ using the octave_call_stack class defined in src/toplev.cc.
Okay, if there is not another way, I will try this.
>
> What information are you really looking for? For a particular call
> to a function, not all functions that could be called are called.
We are writing a testsuite for an octave program. It will be very
helpful if we know for every testcase the caller tree. This tree makes
it possible to say if an error was an error induced by the tested
function directly or by another function called by the tested
function. It makes it possible to decide how important is a function
and how often a function is used.
We need this information not in general but in relation to specific
testcases.
> Octave's interpreter does not currently decide whether an
> identifier is a function or a variable until the code is executed.
> If I
Yep, we want *this* information. A testcase for a specific tested
function triggers the execution of other functions. We need the
caller/calling tree. Here is the scheme:
testsuite -> calls a testcase
testcase -> calls a specific function with specific arguments
(tested function)
specific function -> calls another function if needed
testcase -> collect the caller-tree of specific function, store test
result, caller-tree and so on...
testsuite -> repeat with a new testcase
Bye Andreas
- --
Software Developer / Dipl. Inform. (FH)
Max Planck Institute for Human Cognitive and Brain Sciences
Department of Psychology
Stephanstr. 1a, 04103 Leipzig, Germany
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGKIb9GBhgJGthyeERAuPWAJ9VDw44xP8mWh/KPn1SPmt1Jm/XLACePFvD
rl7o224xPbCKCVU4waVN0+k=
=l5AL
-----END PGP SIGNATURE-----