> Ashok Malhotra wrote: > > The WGs discussed this issue in the meeting on 9/16/2003. > We agreed > > that the description of fn:tokenize was ambiguous and decided to > > clarify it > > Great, thanks. > > > by making it an error for the pattern to match the > zero-length string. > > I'm not sure if I understand you correctly. In order to split > a string > to it's characters the pattern that specifies the separator > must match > the zero-length string (those that are inside the word), no? > > My suggestion was to add > > fn:tokenize("abba", "") returns ("a", "b", "b", "a") > > ... or would that return ("", "a", "b", "b", "a", "") ? > We decided that fn:tokenize("abba", "") should be an error; more specifically, fn:tokenize($in, $regex) is an error if fn:matches("", $regex) is true. This means we are removing the functionality for fn:tokenize to split a string into its individual characters. There are other ways of doing this. We looked at the specs (and actual behavior) for Perl and Java, with different settings of the "limit" parameter, and decided that choosing any one of the available behaviors was likely to be confusing to a significant number of our users. Making it an error keeps our options open for the future, whereas if we get it wrong we are stuck with it for ever. Michael KayReceived on Tuesday, 23 September 2003 05:55:50 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:56:49 UTC