Indeed, currently Char is so restricted. The primary reason is compatibility with Java, so that x10.lang.String can essentially be implemented as java.lang.String.
It does make sense to have a "RichString/RichChar" class as well which supports permits UTF-8. Is there some particular interest in getting this done sooner rather than later...? Best, Vijay Jeff Sweeney wrote: > I am reading the X10 Specification and it seems Char literals are > restricted to ASCII. Is that correct and if so why? > ------------------------------------------------------------------------------ > ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ X10-users mailing list X10-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/x10-users
