We're starting to have real problems with the fact that XNumber in our extension function argument lists only resolves to a double, which leads me to two questions:
1) Is there any sort of standard validator mechanism that we can use to validate that a particular argument is of the right type (not just "number") before we get it out on the other side? 2) Are there any plans to increase the resolution of XObject such that instead of XNumber, we get some more refined types (specifically a problem for us when the integer type we want is larger than a double and doesn't cast well). Also, maybe there's a mechanism for writing custom argument parsers? The documentation isn't that thorough on the subject of extension functions, so I could be missing something entirely. -- Nick
