[
https://issues.apache.org/jira/browse/AXISCPP-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-641.
------------------------------
Resolution: Won't Fix
I am working on revamping tracing so that tracing will already be embedded in
the code. The philosophy that will be taken is that if there is something
pertinent we need to trace, then we will trace it.
> Trace output parameters on methods
> ----------------------------------
>
> Key: AXISCPP-641
> URL: https://issues.apache.org/jira/browse/AXISCPP-641
> Project: Axis-C++
> Issue Type: Bug
> Components: Trace Utility
> Reporter: Mark Whitlock
>
> Currently the trace tool traces all parameters to a method on entry to that
> method, and the return value on exit. However parameters passed by address or
> reference may be updated by the method and so are really output or inout
> parameters. These inout/output parameters should be traced on exit from the
> method. This is slightly harder than it looks since the entry trace must
> cache pointers and references to cope with code like...
> void func(int *p1) {
> *p1 = 5;
> p1 = new int;
> *p1 = 6;
> }
> The caller of this method gets back 5 not 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
