layers of abstraction or simple, flat implementation
1 view
Skip to first unread message
Erik Engbrecht
unread,
Jul 17, 2009, 12:20:41 PM7/17/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to sca...@lists.scalaforge.org, scala...@googlegroups.com
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?
Josh Suereth
unread,
Jul 17, 2009, 1:28:57 PM7/17/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to scala...@googlegroups.com, sca...@lists.scalaforge.org
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.