None from me. There's probably no useful abstraction that could be re-used across .NET + JVM, so I figure a concrete implementation with a nice API is a better way to go (the API could be ported). Seems like a good move.
What do you think of the Stream abstractions?
- Josh
On Fri, Jul 17, 2009 at 12:20 PM, Erik Engbrecht
<erik.engbrecht@...> wrote:
I think the file api I've been working on may have a significant amount of unnecessary complexity stemming from the separation of abstract interfaces defined in traits from the concrete implementations based java.io.File. Right now I think I'm going to chop it all down to a single set of concrete implementations that wrap file.
Any objections?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "The Scala BEAST" group.
To post to this group, send email to scala-beast@...
To unsubscribe from this group, send email to scala-beast%2Bunsubscribe@...
For more options, visit this group at http://groups.google.com/group/scala-beast?hl=en
-~----------~----~----~----~------~----~------~--~---
