Whats more, the VM I/O abstraction is already hiding details of its underlying platforms.
Having another I/O abstraction across multiple VMs sounds like the Fantom Programming Language approach which pushes a unique API across different VM implementations. AFAIK the Clojure approach is more about accessing more low-level parts of the implementing VM with interop typical to the platform. That being said I would not trade slurp/spit for direct java.io access, for example. I'm afraid I'm expressing myself awkwardly. On Mar 9, 9:42 am, Stuart Sierra <the.stuart.sie...@gmail.com> wrote: > Possible to do I/O without any interop ever being called? No. > > Possible to define a standard I/O abstraction that hides the details of the > underlying VM? Yes. But difficult. I/O is a leaky abstraction at the best > of times. > -S -- 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
