From: george.priv@gmail.com
Subject: Re: Address attribute of an overloaded function
Date: Fri, 18 Apr 2008 13:25:09 -0700 (PDT)
Date: 2008-04-18T13:25:09-07:00 [thread overview]
Message-ID: <be945cee-b07b-4e75-b45f-bb033a6f6a5d@e39g2000hsf.googlegroups.com> (raw)
In-Reply-To: 80065d26-869e-4c84-b922-077a0bff6e56@a1g2000hsb.googlegroups.com
On Apr 18, 9:54 am, Ian <ian.will...@techrizon.com> wrote:
> Hi, I've got a window file with 4 different create window procedures.
> I'm trying to put a logger in to allow backtracing by function address
> and name, but I can't get it to take the address of these 4
> functions. I was wondering if any one knew of a way around this. I'm
> inside of the functions when writing to the log so something
> equivalent to C++'s 'this' pointer would work, and the functions
> obviously have different signatures, but I don't know how to specify
> more than the name with 'Address. Any ideas?
I am not sure that is the best approach to do what you want to do. If
you have an exception, you can get stack trace retrieved by
Exception_Information call (you have to enable this function). Or put
tracers in each of your create window procedures.
G.
prev parent reply other threads:[~2008-04-18 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 13:54 Address attribute of an overloaded function Ian
2008-04-18 20:04 ` Adam Beneschan
2008-04-18 20:25 ` george.priv [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox