Re: [xsl] [Xslt 3 Start] Use case for Function Call Invocation

["Christophe Marchand cmarchand@xxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Thanks a lot, mixed-language was indeed not in my mind when reading the 
recommandation !

Christophe

Le 04/02/2021 ` 10:08, Michael Kay mike@xxxxxxxxxxxx a icrit :
> If there's a use case for mixed-language programming, then there's a 
> use case for calling a function written in one language from a 
> function written in another.
>
> It's hard to dream up good use cases for mixed-language programming, 
> because it's something you generally want to avoid when you can. It 
> tends to happen when you are integrating code that already exists, and 
> that uses multiple languages for historic reasons.
>
> Michael Kay
> Saxonica
>
>> On 4 Feb 2021, at 08:08, Christophe Marchand cmarchand@xxxxxxxxxx 
>> <mailto:cmarchand@xxxxxxxxxx> 
>> <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx 
>> <mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>> wrote:
>>
>> Hello !
>>
>> Reading the recommandation, I was not able to imagine a use-case for 
>> Function Call Invocation 
>> <https://www.w3.org/TR/xslt-30/#invoking-initial-function>[1].
>>
>> Recommandation only speeks of raw result, and 2.3.5 section does not 
>> mention a "starting environment".
>>
>> Saxon implementation does not provide a command-line way to start a 
>> XSL with a function call invocation ; there is only an API method to 
>> do so. And in this case, a XDM value is return.
>>
>> Could W3C Xslt group members explain the motivation of such a 
>> starting way ?
>>
>> Does someone has a real use-case of this invocation ?
>>
>> Best regards,
>> Christophe
>>
>> [1] : https://www.w3.org/TR/xslt-30/#invoking-initial-function
>>
>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
>> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/293509> 
>> (by email)
>
> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/2837134> 
> (by email <>)