Hi John,
Zwitserloot is not saying anything meaningful.
He may be trying to say something about the different properties
between scala.List and java.util.List. For example scala.List is
always evaluated in-memory, is immutable and has constant time insert,
while java.util.List says nothing about
Oops, my sock puppet was busted. :-)
On Dec 24, 10:31 am, James Iry wrote:
> Yeah if scala.List is differnt from java.util.List means that Scala is
> incompatible with Java then Java is incompatible with itself because
> it has java.util.List and java.awt.List also it has java.util.Date and
> j
Yeah if scala.List is differnt from java.util.List means that Scala is
incompatible with Java then Java is incompatible with itself because
it has java.util.List and java.awt.List also it has java.util.Date and
java.sql.Date. And a bunch of others. Hahaha.
Thanks for the tip about conversions.
Hi John,
Thanks for investigating rather than taking such claims on face
value. Indeed, the Scala language is compatible with Java's List
hierarchy. As you point out, scala.List is just another class which
you can use or not use.
There is one caveat that brings a small kernel of truth to the
o
I'm really new to Scala so this might not be really good. Riener
made me wonder if Scala was incompatible with Java Lists so I had to
try to see if he was right.
scala> import java.util.List;
import java.util.List
scala> import java.util.ArrayList;
import java.util.ArrayList
scala> val names
Yeah, it's a big mystery.
I guess they have an inferiority complex to beer,
which really is a shame as they can really beat beer
during the work hours. At least at those places that don't allow
drinking at work.
On Dec 24, 1:21 pm, Tom Hawtin wrote:
> On Dec 24, 1:27 am, Hairless_ape wrote:
>
On Dec 24, 1:27 am, Hairless_ape wrote:
> Women.(at least you are on the list)
> Free women.(yes you rank below beer)
I can't understand why they don't want to work with us.
Tom
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
