Michael Kay
Michael Kay
>The current version just returns the content of the persistent module, though in a different form. The suggested version would store the loaded-module under a given name in memory. Can't...
That's what maps are for. Just replace your `store:put` and `store:get` with `map:put` and `map:get`.
>…may be rewritten to and evaluated as: Indeed, it may well be rewritten to `(2, 4, 6, 8, 10)`. Now of course, we could say that the name of the...
> I've already explained that I'm trying to implement polymorfism because that would make my code more transparant and easier to maintain Quite. You've explained how you want to solve...
>My use-case requires that a XML-element is to be processed with a tagname (fn:name#1) specific implementation of the requested functionality Any good reason you aren't using XSLT, which has this...
Indeed, it seems to have gone walkies.
It seems to me that the problem is with the XPath syntax `AbbreviatedStep ::= xxx | SimpleNodeTest` `SimpleNodeTest ::= TypeTest | xxx` `TypeTest ::= RegularItemType | xxx` `RegularItemType ::= xxx...
Addressed by PR #2336
Computing the value from the key, rather than from the input item, seems to benefit some use cases at the expense of others. It makes life more difficult in cases...
>the redefined function can be successfully used to build... all currently provided examples in the FO Spec for the function map:build Looking at this again, many of the rewritten examples...