On 24 Sep 2009, at 11:05 am, Christopher Chittleborough wrote: > The character==grapheme approach makes strings simple and > characters complicated. You'd even need a procedure to > construct character values, something like > (make-character BASE_CHAR LIST_OF_MODIFIERS) > which I for one find mind-boggling. > Then you need procedures to add/remove/reorder modifiers, > etc etc. > > So we have an alternative to the character==codepoint approach. > Is it a good alternative? I don't know.
I think it is... I think the cases were you need to get down into the codepoints are probably rarer than the cases where characters are what you should be concentrating on. And you can still get at the codepoints, when you need to, by picking characters apart. > A good answer to that question will probably have to wait for > Perl 6 to be released and put into widespread use. Yeah, it'll be good to get feedback on that. > If this approach was adopted, support would have to be optional > for the sake of resource-constrained implementations. Well, not necessarily; implementations should be free to provide a subset of the repertoire, such as that provided by ASCII, but they can still provide the API... ABS -- Alaric Snell-Pym Work: http://www.snell-systems.co.uk/ Play: http://www.snell-pym.org.uk/alaric/ Blog: http://www.snell-pym.org.uk/archives/author/alaric/ _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
