- From: <bugzilla@jessica.w3.org>
- Date: Thu, 05 Nov 2015 17:01:08 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29251 --- Comment #8 from Abel Braaksma <abel.braaksma@xs4all.nl> --- I was aiming at / proposing something along these lines: Processors that do not support higher order functions MUST NOT allow any expression that can create functions items (list?) but MAY support function items to be delivered by an external source. It MUST raise a static error when it encounters any function listed in FO31 under "higher-order functions", except fn:function-name and fn:function-arity, which can be used on maps and arrays. Any operation on externally provided function items MUST fail with a dynamic type error, except when such item is tested against a testing expression, such as "instance of", "castable as". Such expressions MAY return false if a function item is encountered. It is implementation dependent whether a processor allows externally supplied function items, for instance through packages or the initial match selection, but it MAY NOT allow any operation other than inspection on such function items. Note: This is similar to saying that any externally supplied function item has type xs:error, and can therefore be tested, but not accessed. Note: This allows processors freedom in choosing whether or not they accept packages that use higher order functions internally, or whether they are made available through public parameters, modes or functions. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 5 November 2015 17:01:11 UTC