On Feb 12, 2009, at 12:53 PM, Phil Hagelberg wrote:
> > > I've got a problem where I have a reader (it's a > java.io.BufferedReader > that came from duck-streams, if that matters at all) and I want to > call > "read" on it. > > I'd expect to be able to do (read (reader my-file)), but this isn't OK > because read needs a java.io.PushbackReader. It seems vaguely wrong > somehow to have a function called "reader" return something that > cannot > be "read" from. > > I took a look at what could be done to fix this. I looked at the clj > definition of read, but it looks like you'd have to turn it into a > multimethod to make it accept readers that aren't PushbackReaders. > Since > read is such a fundamental function, this seems ill-advised. But it > looks to me that you could also solve this problem by adding a > method to > clojure.lang.LispReader that could accept other kinds of readers and > wrap them in a PushbackReader without modifying any existing code. > > Does this seem like a decent idea? Yes. Issue/patch welcome. Rich --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
