Saxon's adaptive serialization of an anonymous functions
Added by Martin Honnen over 2 years ago
With SaxonCS and SaxonJ, the adpative serialization of e.g. random-number-generator()
gives e.g. map{"next":Q{anon}anon#0,"number":4.541541260138987e-1,"permute":Q{anon}anon#1}
.
Someone on Twitter thinks the Q{anon}
is suspicious or giving the wrong context these days. Might be more of a joke.
Is there a way to get SaxonCS and/or Java to output something clearer/cleaner like BaseX (anonymous-function)#0
or SaxonJS (anonymous function)#0
do?
Replies (4)
Please register to reply
RE: Saxon's adaptive serialization of an anonymous functions - Added by Michael Kay over 2 years ago
🙀
RE: Saxon's adaptive serialization of an anonymous functions - Added by Michael Kay over 2 years ago
It seems this designation is used only for system-created anonymous functions (specifically, instances of CallableFunction); for user-created functions such as
function(){3}
the representation is (anonymous-function)#0
RE: Saxon's adaptive serialization of an anonymous functions - Added by Martin Honnen over 2 years ago
Yes, right, I kind of inferred from that sample that the format is generally used for anonymous functions but later found that SaxonJS/SaxonCS do use (anonymous-function)
for user created functions. So the impact is much smaller than I initially thought.
RE: Saxon's adaptive serialization of an anonymous functions - Added by Michael Kay over 2 years ago
I shall change it to use NamespaceConstant.ANONYMOUS
in 12.x.
Please register to reply