This is exactly what I was going to propose, and I think its what Tom
actually told me one drunken evening and has been stuck in my head.
MD
On 4 Jul 2007, at 09:27, Tom Chiverton wrote:
> On Tuesday 03 Jul 2007, Michael Dinowitz wrote:
>> what I know, the answer is no but I'm hoping I'm wron
On Tuesday 03 Jul 2007, Michael Dinowitz wrote:
> what I know, the answer is no but I'm hoping I'm wrong. I have to write a
> trace/debug for mach-ii and need to know what component was called, from
> where, what was passed and what errors occurred (and were caught with a
> try/catch).
> Fun. :(
T
nt: Tuesday, July 03, 2007 2:49 PM
To: CF-Talk
Subject: Does a component know its parent?
Is there any way for a component to 'know' where it was called from? From
what I know, the answer is no but I'm hoping I'm wrong. I have to write a
trace/debug for mach-ii and need to kn
> Is there any way for a component to 'know' where it was called from? From
> what I know, the answer is no but I'm hoping I'm wrong. I have to write a
> trace/debug for mach-ii and need to know what component was called, from
> where, what was passed and what errors occurred (and were caught with
a component know its parent?
Is there any way for a component to 'know' where it was called from? From what
I know, the answer is no but I'm hoping I'm wrong. I have to write a
trace/debug for mach-ii and need to know what component was called, from where,
what was pa
Is there any way for a component to 'know' where it was called from? From
what I know, the answer is no but I'm hoping I'm wrong. I have to write a
trace/debug for mach-ii and need to know what component was called, from
where, what was passed and what errors occurred (and were caught with a
try/ca
6 matches
Mail list logo
