| Re: call_procedure with a dynamically created arguments list? [message #50605 is a reply to message #50604] |
Fri, 06 October 2006 16:10   |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Dometz writes:
> Basically, all I am doing is:
> I automatically parse someones code and replace certain calls (ex:
> read_png) with wrapper functions. Inside of these wrapper functions, I
> record then timestamp when they were called, with what arguments etc.
> Now all this is supposed to happen transparent to the user. Basically,
> the user shouldnt even know that this happening or at least it shouldnt
> affect him.
Alright, this is sounding more and more like something that
is being funded by Homeland Security, and I want nothing
more to do with it. I really don't think such a thing is
possible in a weakly typed language in which parameters
can be input or output or both at the same time. Which
"parameter" are you going to store anyway? The one that
went in, or the one that came out? If you are going to
store "all" of them, then the user is going to know about
it, despite your best efforts, because memory usage is
going to balloon so much he won't be able to get any work
done anymore.
I think I would be angling for a new project.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
