IMO Unit Tests are better for testing if functions are written correctly. Errors should be meaningful enough that you don't need parameter values, but you *could* output that information with the most verbose trace level - but this is the same advice you've been getting from everybody else. I'll leave these important architectual decisions up to you...
Brian Franklin Gray wrote:
Ok....now...how about the part to write. It's been a lot time but I vaguely remember coming across something that could access parameters of a function. If I could build a function to call at the beginning of each function and it would check to see if the trace was turned on and if so it would loop through all the parameters of the calling function (the one I want to log the parameter values) then that would save a lot of typing and centralize the process. Anybody know of such a thing? It's been so long I don't even remember what to search for. The reason I want to log parameters is because though my years of work, I've found that to find a bug, the parameters to a function is the second best piece of information, first being the line of the error and the error description which of course is easy to retrieve. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
=================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
