Quantcast

Method trace?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Method trace?

James Ladd
Would it help anyone if you were able to run Redline with a command line switch that
made a method trace out to the console?

The trace would be an output as each method is entered, initially with just the method name.

Please don't say yes if you think you 'might' want this, rather say yes if you need this today.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Method trace?

JONNALAGADDA Srinivas
On Saturday, 29 December 2012 10:31:46 UTC+5:30, jamesl wrote:
Would it help anyone if you were able to run Redline with a command line switch that
made a method trace out to the console?

The trace would be an output as each method is entered, initially with just the method name.

Please don't say yes if you think you 'might' want this, rather say yes if you need this today.

        Methinks a trace mechanism such as the one you propose does come handy when debugging cases like Behavior>>inheritsFrom: which I described in a different post.

        However, every feature comes at a cost!  A simple reflexive way to weigh the cost and the intended benefit of this feature can be the answer to: does James incur a considerable amount of time on a continual basis, owing to the lack of this trace mechanism?

-- |0|0|
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Method trace?

James Ladd
And will ppl read the trace before saying there is a bug/issue :)

It isn't hard to add and it will save time 

Sent from Hyperspace.

On 31/12/2012, at 3:51 PM, JONNALAGADDA Srinivas <[hidden email]> wrote:

On Saturday, 29 December 2012 10:31:46 UTC+5:30, jamesl wrote:
Would it help anyone if you were able to run Redline with a command line switch that
made a method trace out to the console?

The trace would be an output as each method is entered, initially with just the method name.

Please don't say yes if you think you 'might' want this, rather say yes if you need this today.

        Methinks a trace mechanism such as the one you propose does come handy when debugging cases like Behavior>>inheritsFrom: which I described in a different post.

        However, every feature comes at a cost!  A simple reflexive way to weigh the cost and the intended benefit of this feature can be the answer to: does James incur a considerable amount of time on a continual basis, owing to the lack of this trace mechanism?

-- |0|0|
Loading...