Talk:Stack traces: Difference between revisions
Content added Content deleted
(More info?) |
(→More info?: respond...) |
||
| Line 1: | Line 1: | ||
==More info?== |
==More info?== |
||
How about changing the task to print a stack trace from within g() which is called from f() - and actually show sample output for inter-language ccomparison? --[[User:Paddy3118|Paddy3118]] 18:13, 5 June 2009 (UTC) |
How about changing the task to print a stack trace from within g() which is called from f() - and actually show sample output for inter-language ccomparison? --[[User:Paddy3118|Paddy3118]] 18:13, 5 June 2009 (UTC) |
||
: I don't particularly want to constrain what people call the functions as precise comparisons aren't the point of the task (the point: show facilities for debugging without having to use an external debugger) but showing what the output is is a very good idea. —[[User:Dkf|Donal Fellows]] 07:52, 6 June 2009 (UTC) |
|||
Revision as of 07:52, 6 June 2009
More info?
How about changing the task to print a stack trace from within g() which is called from f() - and actually show sample output for inter-language ccomparison? --Paddy3118 18:13, 5 June 2009 (UTC)
- I don't particularly want to constrain what people call the functions as precise comparisons aren't the point of the task (the point: show facilities for debugging without having to use an external debugger) but showing what the output is is a very good idea. —Donal Fellows 07:52, 6 June 2009 (UTC)