Merged revisions 24494-24498 via svnmerge from

https://lampsvn.epfl.ch/svn-repos/scala/scala/trunk

........
  r24494 | extempore | 2011-03-18 19:23:14 +0100 (Fri, 18 Mar 2011) | 17 lines

  Accumulated work on fsc. Cleans up a bunch of things, and adds the
  following new options.

    -ipv4 Use IPv4 rather than IPv6 for the server socket absolute-cp
    -Make classpath elements absolute paths before sending to server
    -max-idle Set idle timeout in minutes for fsc (use 0 for no timeout)

  My question marks are what are the right defaults for the first two.
  Former behavior is to absolutize the classpath always and never prefer
  IPv4 sockets. I changed the default to not absolutize the classpath,
  with the option if you need it; I left the system default in place for
  the socket creation, but I have a feeling we should default to IPv4.
  My only hesitation is that the only way to request an IPv4 socket from
  java involves mutating a global system property. (Robustness FTW.) So
  for now, you have to give -ipv4.

  Closes #3626, #3785, #3788, #3789. Review by community. ........
r24495 | extempore | 2011-03-18 20:06:22 +0100 (Fri, 18 Mar 2011) | 2
lines

  Improved the error message when one gives invalid options to scala.
Similar improvements for scalac/fsc/etc has to wait. No review. ........
r24496 | prokopec | 2011-03-18 20:07:38 +0100 (Fri, 18 Mar 2011) | 25
lines

  Removing toPar* methods, since we've agreed they're difficult to:

  - underestand
  - maintain

  Also, changed the docs and some tests appropriately.

  Description:
  1) Every collection is now parallelizable - switch to the parallel version of the collection is done via `par`.

  - Traversable collections and iterators have `par` return a parallel collection of type `ParIterable[A]` with the implementation being the representative of `ParIterable`s (currently, `ParArray`).
  - Iterable collections do the same thing.
  - Sequences refine `par`'s returns type to `ParSeq[A]`.
  - Maps and sets do a similar thing.

  The above means that the contract for `par` changed - it is no longer guaranteed to be O(1), nor reflect the same underlying data, as was the case for mutable collections before. Method `par` is now at worst linear.

  Furthermore, specific collection implementations override `par` to a more efficient alternative - instead of copying the dataset, the dataset is shared between the old and the new version. Implementation complexity may be sublinear or constant in these cases, and the underlying data structure may be shared. Currently, these data structures include parallel arrays, maps and sets, vectors, hash trie maps and sets, and ranges.

  Finally, parallel collections implement `par` trivially.

  2) Methods `toMap`, `toSet`, `toSeq` and `toIterable` have been
refined for parallel collections to switch between collection types,
however, they never switch an implementation from parallel to
sequential. They may or may not copy the elements, as is the case with
sequential variants of these methods.

  3) The preferred way to switch between different collection types,
whether maps, sets and seqs, or parallel and sequential, is now via use
of methods `toIterable`, `toSeq`, `toSet` and `toMap` in combination
with `par` and `seq`.

  Review by odersky.
........
  r24497 | extempore | 2011-03-18 22:07:37 +0100 (Fri, 18 Mar 2011) | 2 lines

  A minor overhaul of power mode. I'm going to document it any minute
now. No review. ........ r24498 | extempore | 2011-03-18 22:22:57 +0100
(Fri, 18 Mar 2011) | 1 line

  Little tweak for failing test, no review.
........

0 files changed, 0 insertions, 0 deletions