This page is no longer maintained — Please continue to the home page at www.scala-lang.org

Re: Scala IO step 2

3 replies
Joshua.Suereth
Joined: 2008-09-02,
User offline. Last seen 32 weeks 5 days ago.
Google also recently released some "commons" library that includes I/O ideas.  Some of these are functional, and I think need to be thought through.

I'm very against whole-sale duplicating the API, as I'd like to see something very Scala come out.  However as a first cut, great work!  I'll dig through this tonight, if I can find some time.


- Josh

On Thu, Sep 17, 2009 at 5:04 PM, Jesse Eichar <jeichar.w@gmail.com> wrote:
I have updated the google spreadsheet with the API from the Java 7 openJDK Javadocs and mapped all the methods to the ones I found in the very briefly published API in Scala 2.8.  I have been for some odd reason unable to generate the docs from the Scala.IO clone I have.
Next steps:
  • Prioritize the missing functionality
  • Make a report listing the areas of the Scala.io API that could cause problems in the future.  Although I must say that for the most part it aligns very well with the API.  The biggest difference is that it is not as complete yet.  Not surprising.
  • Discuss some of the issues I raise.
  • Probably remove more items to out of scope status.
  • continue to flesh out implementation.
If I got anything stupidly wrong or if you can think of a better way of showing this information than a spreadsheet please let me know and I will do my best to fix the issues.
Spreadsheet link: http://spreadsheets.google.com/ccc?key=0Ag5uUcFLY2mpdC1TX3BzUEE0UVhxeFNjcFZkV3pHS3c&hl=en


Jesse

Jesse Eichar
Joined: 2008-12-20,
User offline. Last seen 42 years 45 weeks ago.
Scala IO step 2
I have updated the google spreadsheet with the API from the Java 7 openJDK Javadocs and mapped all the methods to the ones I found in the very briefly published API in Scala 2.8.  I have been for some odd reason unable to generate the docs from the Scala.IO clone I have.
Next steps:
  • Prioritize the missing functionality
  • Make a report listing the areas of the Scala.io API that could cause problems in the future.  Although I must say that for the most part it aligns very well with the API.  The biggest difference is that it is not as complete yet.  Not surprising.
  • Discuss some of the issues I raise.
  • Probably remove more items to out of scope status.
  • continue to flesh out implementation.
If I got anything stupidly wrong or if you can think of a better way of showing this information than a spreadsheet please let me know and I will do my best to fix the issues.
Spreadsheet link: http://spreadsheets.google.com/ccc?key=0Ag5uUcFLY2mpdC1TX3BzUEE0UVhxeFNjcFZkV3pHS3c&hl=en


Jesse
Jesse Eichar
Joined: 2008-12-20,
User offline. Last seen 42 years 45 weeks ago.
Re: Scala IO step 2
Do you have a link to the Google commons/IO library?  I am having difficulty finding it.  
I also want to review other libraries such as those in other functional libraries to see if there are some ideas that could be beneficial for the Scala library.  I am a Java developer primarily though so I would appreciate some ideas of good functional IO libraries.
Jesse
On Thu, Sep 17, 2009 at 11:06 PM, Josh Suereth <joshua.suereth@gmail.com> wrote:
Google also recently released some "commons" library that includes I/O ideas.  Some of these are functional, and I think need to be thought through.

I'm very against whole-sale duplicating the API, as I'd like to see something very Scala come out.  However as a first cut, great work!  I'll dig through this tonight, if I can find some time.


- Josh

On Thu, Sep 17, 2009 at 5:04 PM, Jesse Eichar <jeichar.w@gmail.com> wrote:
I have updated the google spreadsheet with the API from the Java 7 openJDK Javadocs and mapped all the methods to the ones I found in the very briefly published API in Scala 2.8.  I have been for some odd reason unable to generate the docs from the Scala.IO clone I have.
Next steps:
  • Prioritize the missing functionality
  • Make a report listing the areas of the Scala.io API that could cause problems in the future.  Although I must say that for the most part it aligns very well with the API.  The biggest difference is that it is not as complete yet.  Not surprising.
  • Discuss some of the issues I raise.
  • Probably remove more items to out of scope status.
  • continue to flesh out implementation.
If I got anything stupidly wrong or if you can think of a better way of showing this information than a spreadsheet please let me know and I will do my best to fix the issues.
Spreadsheet link: http://spreadsheets.google.com/ccc?key=0Ag5uUcFLY2mpdC1TX3BzUEE0UVhxeFNjcFZkV3pHS3c&hl=en


Jesse


Jorge Ortiz
Joined: 2008-12-16,
User offline. Last seen 29 weeks 4 days ago.
Re: Scala IO step 2
http://code.google.com/p/guava-libraries/

On Thu, Sep 17, 2009 at 11:36 PM, Jesse Eichar <jeichar.w@gmail.com> wrote:
Do you have a link to the Google commons/IO library?  I am having difficulty finding it.  
I also want to review other libraries such as those in other functional libraries to see if there are some ideas that could be beneficial for the Scala library.  I am a Java developer primarily though so I would appreciate some ideas of good functional IO libraries.
Jesse
On Thu, Sep 17, 2009 at 11:06 PM, Josh Suereth <joshua.suereth@gmail.com> wrote:
Google also recently released some "commons" library that includes I/O ideas.  Some of these are functional, and I think need to be thought through.

I'm very against whole-sale duplicating the API, as I'd like to see something very Scala come out.  However as a first cut, great work!  I'll dig through this tonight, if I can find some time.


- Josh

On Thu, Sep 17, 2009 at 5:04 PM, Jesse Eichar <jeichar.w@gmail.com> wrote:
I have updated the google spreadsheet with the API from the Java 7 openJDK Javadocs and mapped all the methods to the ones I found in the very briefly published API in Scala 2.8.  I have been for some odd reason unable to generate the docs from the Scala.IO clone I have.
Next steps:
  • Prioritize the missing functionality
  • Make a report listing the areas of the Scala.io API that could cause problems in the future.  Although I must say that for the most part it aligns very well with the API.  The biggest difference is that it is not as complete yet.  Not surprising.
  • Discuss some of the issues I raise.
  • Probably remove more items to out of scope status.
  • continue to flesh out implementation.
If I got anything stupidly wrong or if you can think of a better way of showing this information than a spreadsheet please let me know and I will do my best to fix the issues.
Spreadsheet link: http://spreadsheets.google.com/ccc?key=0Ag5uUcFLY2mpdC1TX3BzUEE0UVhxeFNjcFZkV3pHS3c&hl=en


Jesse



Copyright © 2012 École Polytechnique Fédérale de Lausanne (EPFL), Lausanne, Switzerland