Re: Using libunistring for string comparisons et al

2011-03-11 Thread Mark H Weaver
I wrote: > I'm aware that this proposal will be very controversial, but starting in > Guile 2.2, I think we ought to consider storing strings internally in > UTF-8, as is done in Gauche. This would of course make string-ref and > string-set! into O(n) operations. However, I claim that any code th

Re: Using libunistring for string comparisons et al

2011-03-11 Thread Mark H Weaver
Sorry, I accidentally sent out an only partly-written draft message. Please disregard for now; I will finish writing it later. Mark

Using libunistring for string comparisons et al

2011-03-11 Thread Mark H Weaver
Mike Gran writes: > [...] But doing the upper->lower operation picks > up a few more of the corner cases, like U+03C2 GREEK > SMALL LETTER FINAL SIGMA and U+03C3 GREEK SMALL LETTER SIGMA > which are the same letter with different representations, > or U+00B5 MICRO SIGN and U+039C GREEK SMALL LETTE

SRFI-23

2011-03-11 Thread Noah Lavine
Hello all, Guile supports srfi-23 (the `error' procedure), and probably has forever, but it's not documented. This patch adds a note in the manual saying we support it, and also adds srfi-23 to our list of cond-expand features that we support. I think this is safe to apply to stable-2.0. Noah

Re: The usage of -dtrace-scheme-coverage in Lilypond

2011-03-11 Thread Han-Wen Nienhuys
On Fri, Mar 11, 2011 at 12:21 AM, zhangxy wrote: > Dear hanwen, > Now I want to analyze the test coverage of Lilypond. I find the option > -dtrace-scheme-coverage. It says that the option can record coverage of > Scheme files in `FILE.cov'. Then I do the following >> >> lilypond -dtrace-scheme-cov