XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Re: xml-dev Digest 24 Mar 2010 11:49:31 -0000 Issue2307

I disagree that this specifies the order of execution.

>>  example 3: for i in 1..length(array) yield function(a[i])

The results must be in order but the execution need not.




-------------------------
David A. Lee
dlee@calldei.com
http://www.calldei.com
http://www.xmlsh.org


On 3/24/2010 10:25 AM, Nicholas Sushkin wrote:
> On Wednesday 24 March 2010 07:49:31 xml-dev-digest-help@lists.xml.org wrote:
>    
>> If yes, then anything which forces sequential processing is, by definition,
>> not declarative. Do you agree?
>>      
> I disagree. Declarative processing just defines what you need to compute
> without necessarily providing a sequential algorithm to do it. However, you
> may declare the process to be sequential.
>
> For example, all of the examples below are declarative ways to apply a
> function to each element of the array, but only the last one specifying the
> order of execution.
>
> example 1: map(function, array)
> example 2: foreach _ in array yield function(_);
> example 3: for i in 1..length(array) yield function(a[i])
>
>    


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS