Project

Profile

Help

Patch #1410

closed

extension functions with defered argument evaluation

Added by Anonymous over 19 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Internals
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Legacy ID:
sf-1064855
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

SourceForge user: gschadow

Michael, this is the patch that implements defered

argument evaluation in extension functions (the "special

form" stuff that I brought up in connection with my

closure function -- but without any of the closure

business.)

The patch is straight-forward and I ask you to pretty

please adopt this feature into your code.

On the user end it works by sending argument

Expressions unevaluated to any formal argument of type

Expression. This requires that the first argument is

XPathContext. Mixed argument lists are possible.

Expression arguments have highest preference for the

argument conversion.

I will follow up with a variable length argument list

handler, that would match all remaining actual

arguments to a final formal argument of type Expression

[].

thanks,

-Gunther


Files

Actions #1

Updated by Anonymous over 19 years ago

SourceForge user: gschadow

Logged In: YES

user_id=575520

BTW: this is against saxon-8.1.1 of course

Actions #2

Updated by Michael Kay almost 11 years ago

  • Status changed from New to Closed

Closed, time-expired. The requirement is better handled these days by using XPath 3.0 higher order functions.

Please register to edit this issue

Also available in: Atom PDF