On Monday, December 8, 2014 9:32:28 AM UTC-5, Las wrote: > Still, this is awkward, verbose, and prevents the (nontrivial) use of edn >> in a platform-neutral way by referring only to Clojure functions without >> direct interop. Well, except for the even more awkward workaround of slurp >> and read-string, with the accompanying need to hold the entire file in >> memory *twice* for a short time. >> > >> As far as why it requires a PushbackReader, I didn't design the API. >>> Yes, some things in Clojure require using Java interop, and in many (but >>> not all) cases, file I/O requires it. >>> >> >> Perhaps io/reader should output a PushbackReader, if only for >> convenience's sake. >> > io/reader is not meant to be used solely as an input to edn/read. >
AFAICT, PushbackReader is substitutable anywhere a reader is expected, but apparently a plain unwrapped BufferedReader is not. -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
