Michael Kay

It seems that the proposed backslash-notation is not defining `\[1, 2, 3]\` as an expression, but rather as a modifier of the syntax of a static function call which somehow...

>C# has different semantics to Java because the Current item is a property and is named Current. This allows a user to access Current multiple times in the function without...

>In short, a generator looks like a function but behaves like an [iterator](https://en.wikipedia.org/wiki/Iterator).” Looking at this thread again, what's being described here looks much more like an iterator than a...

But I wonder also whether we could find a way of writing iterators in generator/coroutine programming style, as a function which "yields" items one at a time? There's a relationship...

Certainly Java and C# get great value from the Iterator/Enumerator concept. However, they are procedural stateful languages, and therefore have limited scope for lazy evaluation. Many of the benefits of...

While conversion to/from Unix dates and times might be very handy for many users, it's not the only way of representing a date/time as an integer, so I think it...

An alternative approach would be to have a function `fn:seconds` that returns an `xs:dayTimeDuration` of a given length, and perhaps a function `fn:unix-epoch()` that returns the relevant dateTime value, and...

Yes, interactive debugging of this kind of thing can be very useful, but I think it's outside our scope. In many cases (like the one I was dealing with yesterday)...

The proposal differs from XQueryX in that the body of a function is written in pure human-readable XPath. XQueryX was never intended to be human-readable or writable. It differs from...

This is about providing a mechanism for use by people who (like Mary) want to define a function library that can be used both in XSLT and in XQuery applications,...