> and I agree with you that this particular problem > which arises when (@colspan+1) returns a double rather than an integer is > one that we ought to fix. I'm glad to hear that. > (The other one I would like to fix is that > concat() should implicitly convert its arguments to strings - even Java does > this). That would be useful, but why just concat? Why shouldn't _all_ functions taking string arguments convert their arguments to strings? What's different about the concat function. (It's not very different from string-join for example) > We have looked at most of the solutions you propose. I'm not surprised by that:-) > In my view the right (i.e. least problematic) answer is (2). If that was the final decision (I accept that yours was a personal response not a formal group one) I'd be happy to accept that resolution. The current type system modified as in (2) would still be a long way from my preferred type system (which would be closer to Xpath 1:-) but given where we are now, it would I think remove many of the more severe usability problems with the current system. David ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________Received on Tuesday, 20 April 2004 08:19:49 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:08 GMT