- From: Christian Grün <cg@basex.org>
- Date: Wed, 2 Dec 2020 11:53:59 +0100
- To: public-xslt-40@w3.org
The description for fn:stack-trace is fairly general and vague [1]. I think that’s just fine, as the specs do not prescribe how to implement function invocations. “Stack trace” implies to me that the function will return the call stack (i.e., the stack of invoked functions). As this may only be fully possible if functions are not inlined at compile time, code might need to be compiled differently whenever a stack trace request is found… and so forth. The name also implies to me that the function should return nothing else. However, it could be helpful to get a list of bound variables with their values at runtime. Maybe we can find a more general name, such as fn:debug or fn:runtime-trace? Cheers, Christian [1] Returns implementation-dependent information about the current state of execution.
Received on Wednesday, 2 December 2020 10:55:21 UTC