RE: Re: Random module
"Jim Fuller" <[email protected]>
| Newsgroups | gmane.text.xml.xslt.extensions |
|---|---|
| Message-ID | <[email protected]> |
+1 to clarification which was my original assumption. thx Craig ! j -----Original Message----- From: Dimitre Novatchev [mailto:[email protected]] Sent: 21 October 2003 15:02 To: Craig Stewart; [email protected] Subject: Re: [exslt] Re: Random module Hi Craig, > I've changed the function from 'other' to 'core' and have altered the > output to 'number+'. > > How's that look? It is OK now. But... It seems nobody noticed until now that we do not have number+ or double* in XPath 1.0 For XPath/XSLT 1.0 we'll have to use the not so nice but commonly used (e.g. in the Sets module) node-set. Each node in the returned node-set has a text child, whose value is a random number. Everyone, please, indicate your approval of this clarification. On another topic, I would suggest that on the central page some more recent news be displayed -- e.g. the most rescent announced EXSLT implementations for .Net and the Sets and Common modules implemented for .MSXML4 ===== Cheers, Dimitre Novatchev. http://fxsl.sourceforge.net/ -- the home of FXSL __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com _______________________________________________ exslt mailing list [email protected] http://www.exslt.org/list This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient please contact the sender immediately. Any disclosure, copying, distribution or any other use of this communication is strictly prohibited and may be unlawful. Stuart Lawrence Marketing Communications Limited reserves the right to monitor and intercept communications for unlawful business purposes. This also confirms that this message has been swept for viruses, although Stuart Lawrence Marketing Communications Limited accepts no responsibility for any loss or damage resulting directly or indirectly from the use of this email or contents.