> I see 9 on 1.2 as well. The call to .length is a Java interop form, so it is > very difficult to imagine how this might change.
My guess is rather that the string is interpreted differently by the reader; the 27 is almost certainly correct; the question is how the string is originally constructed. I had a very quick look at LispReader (not its history) and didn't see anything obvious (in 30 seconds anyway). What are the chances the reader has changed with respect to assumptions about the encoding of *in*? The behavior experienced by the OP may be the result of his native system encoding being, say, shift_JIS or something which is then interpreted as, say, UTF-8 and luckily/unluckily not failing, instead producing a valid unicode string of length 27. -- / Peter Schuller -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
