Ismael Juma | 1 Dec 2009 10:00
Picon

Nightlies not running on Hudson.

Hi all,

Looking at Hudson[1], the last main nightly build was on the 29th of
November. However, there were a few commits yesterday, so it seems like
there should have been a new build today. Is there a problem (and if so,
is it a known one) or am I missing something?

Best,
Ismael

[1] http://scala-webapps.epfl.ch/hudson/job/scala-nightly-main/

Lukas Rytz | 1 Dec 2009 10:24
Picon
Picon
Favicon
Gravatar

Re: Nightlies not running on Hudson.

Tomcat was making problems. Now, after a re-start, everything should be on again.

On Tue, Dec 1, 2009 at 10:00, Ismael Juma <mlists <at> juma.me.uk> wrote:
Hi all,

Looking at Hudson[1], the last main nightly build was on the 29th of
November. However, there were a few commits yesterday, so it seems like
there should have been a new build today. Is there a problem (and if so,
is it a known one) or am I missing something?

Best,
Ismael

[1] http://scala-webapps.epfl.ch/hudson/job/scala-nightly-main/


No.0023 (Openbsd Engine | 1 Dec 2009 10:29
Picon

Let's connect on LinkedIn

LinkedIn

I'd like to add you to my professional network on LinkedIn.

- No.0023 (Openbsd Engine)

Confirm that you know No.0023 (Openbsd Engine)

Every day, millions of professionals like No.0023 (Openbsd Engine) use LinkedIn to connect with colleagues, find experts, and explore opportunities.

© 2009, LinkedIn Corporation

Ismael Juma | 1 Dec 2009 10:30
Picon

Re: Nightlies not running on Hudson.

On Tue, 2009-12-01 at 10:24 +0100, Lukas Rytz wrote:
> Tomcat was making problems. Now, after a re-start, everything should
> be on again.

Thanks.

Ismael

Kohler, Markus | 1 Dec 2009 11:22
Picon
Favicon

Re: jvm5 build should be default?

David Pollak <feeder.of.the.bears <at> gmail.com> writes:
 
>
>
> I cannot agree with this more.
>
> I'm currently working with a bunch of SAP folks on the ESME related stuff.
> NetWeaver (SAP's app server) runs on JDK 1.5.  It's no end of pain to have
> to specify a JDK5 version.  The cost and barrier to folks who are new to
> Scala is non-trivial and the initial experience is not ideal.
 
+1
IMHO with static typing, Scala has at least one major advantage in becoming the  
new JVM based language for  the Enterprise world.
 
SAP still has a lot of customers on JDK 1.4, slowly migrating to JDK 1.5.
Enterprise customers are only slowly moving to newer JDK's. Support for JDK 1.5
is therefore crucial to get adoption (IMHO).
 
Regards,
 
 
 
 
Markus Kohler | 1 Dec 2009 12:42
Picon
Gravatar

mkString implementation for collections

Hi all,

During some performance tests for Apache esme (http://incubator.apache.org/esme/), I noticed that the implementation of def mkString(start: String, sep: String, end: Stringin


is suboptimal in regards to memory allocation frequency. 

The reason is that it uses the default constructor of StringBuilder. 
I haven't checked how it is in Scala, but in Java StringBuilder's default size is 16 characters. We noticed that in ESME this would lead to to frequent calls to expand the StringBuilders char[] which freshly allocates and char[] and copies the char over. 
 
I understand that in Iterator itself, one can hardly have a more efficient implementation, but it seems to me that in at least some Collections  this could be improved. 

I'm new here, and would like to hear your opinions about whether you think this is a bug, and also what would be the recommended way to avoid this issue. 

Regards,
Markus


"The best way to predict the future is to invent it" -- Alan Kay
David Jaquay | 1 Dec 2009 15:31
Picon

Re: Shutting down w/multiple actors

On Sat, Nov 28, 2009 at 11:08 PM, Bill Burdick <bill.burdick <at> gmail.com> wrote:
In Xus, I needed to control shutdown precisely.  You may not like this solution, but this is what I came up with after trying a bunch of different approaches:


1) Use DaemonActors instead of regular ones.  This prevents actors from keeping a program running.


At least what I've seen so far, it looks like my actors are already running as daemon threads.  My "problem" (or at least the behavior I'm observing) is that when my main thread quits, all the actors quit as well, before they're done with what's in their queues.  In fact, 3 of my 5 actors (all of which are "receive" actors, not "react") have no code to cause/allow them to quit, so my impression is that they are still running when the program exits.

Is this a behavior difference between different Scala versions?  I'm running 2.7.5final out of Ubuntu's repos, if that matters.

Otherwise, I seem to be doing things much like all three of you (Kal, Graham and Bill).

Thanks,
Dave


martin odersky | 1 Dec 2009 15:56
Picon
Picon
Favicon

Re: Re: jvm5 build should be default?

We just decided in the Scala meeting to keep Java 1.5 as not only the
default, but the only version required by Scala 2.8. We will make use
of dynamic class loading and reflection to load the real FJ  framework
instead of its 1.5 backport or java.util.concurrent. This decision
holds unless some unexpected problems come up with this dynamic
loading scheme.

Cheers

 -- Martin

Daniel Mahler | 1 Dec 2009 16:46
Picon

Re: scala.reflect.Manifest status

Hi Paul,

Thanks. Do you think your code is likely to make it into 2.8.0 final?
If not , does anybody know when a fully implemented Manifest is expected?
Alternatively is there a way to do something like my typeCheck example
without manifests?

thanks
Daniel

On Sat, Nov 28, 2009 at 7:25 AM, Paul Phillips <paulp <at> improving.org> wrote:
>
> On Sat, Nov 28, 2009 at 01:53:32AM +0100, Daniel Mahler wrote:
>> Is there another way to do the following:
>>
>>  def manifestOf[T](implicit m : Manifest[T]) = m
>>
>>  def typeCheck[T](implicit m : Manifest[T]) = (
>>    if (m <:< manifestOf[AnyVal]) "Value"
>>    else if (m <:< manifestOf[AnyRef]) "Reference"
>>    else "???")
>>
>> scala> typeCheck[Int]
>> res8: java.lang.String = ???
>
> It looks like most of the manifest stuff is just unimplemented.  I took
> a swing at it just now but I could be way off of how things are supposed
> to be done so I won't check anything in.  With this patch in place it's
> pretty close to working how I'd expect it to, with two missing pieces I
> can think of at this second: a) invariant collections give the wrong
> answer and b) manifestOf[Object] is not selecting Manifest.Object, which
> is busting an assumption of mine.
>
> Here's the test case I have mostly passing.  (I'm not sure these are all
> the right answers, but these are the answers...)
>
>  def f1 = List(
>    manifestOf[java.lang.Integer] <:< manifestOf[Any],
>    manifestOf[java.lang.Integer] <:< manifestOf[AnyRef],
>    manifestOf[java.lang.Integer] <:< manifestOf[AnyVal]
>  )
>
>  def f2 = List(
>    manifestOf[Int] <:< manifestOf[Any],
>    manifestOf[Int] <:< manifestOf[AnyVal],
>    !(manifestOf[Int] <:< manifestOf[AnyRef])
>  )
>
>  def f3 = List(
>    manifestOf[List[String]] <:< manifestOf[List[Any]],
>    manifestOf[List[String]] <:< manifestOf[AnyRef],
>    !(manifestOf[List[Any]] <:< manifestOf[List[String]])
>  )
>
>  // doesn't work yet, variance
>  // def f4 = List(
>  //   !(manifestOf[Set[Any]] <:< manifestOf[Set[String]]),
>  //   !(manifestOf[List[String]] <:< manifestOf[List[Any]])
>  // ) foreach (x => assert(x))
>
>  def f5 = List(
>    manifestOf[Nothing] <:< manifestOf[Any],
>    manifestOf[Nothing] <:< manifestOf[AnyVal],
>    manifestOf[Nothing] <:< manifestOf[AnyRef],
>    manifestOf[Nothing] <:< manifestOf[String],
>    manifestOf[Nothing] <:< manifestOf[List[String]],
>    manifestOf[Nothing] <:< manifestOf[Null]
>  )
>
>  def f6 = List(
>    manifestOf[Null] <:< manifestOf[Any],
>    !(manifestOf[Null] <:< manifestOf[AnyVal]),
>    manifestOf[Null] <:< manifestOf[AnyRef],
>    manifestOf[Null] <:< manifestOf[String],
>    manifestOf[Null] <:< manifestOf[List[String]],
>    manifestOf[Null] <:< manifestOf[Null],
>    !(manifestOf[Null] <:< manifestOf[Nothing])
>  )
>
>  def main(args: Array[String]): Unit = {
>    List(f1, f2, f3, f5, f6).flatten foreach (x => assert(x))
>  }
>
> --
> Paul Phillips      | A national political campaign is better than the
> In Theory          | best circus ever heard of, with a mass baptism and
> Empiricist         | a couple of hangings thrown in.
> pp: i haul pills   |     -- H. L. Mencken
>

Walter Chang | 1 Dec 2009 16:49
Picon
Gravatar

Re: Re: jvm5 build should be default?

how much of this is going to impact scala-based development on google
android?  i don't know the extents of the changes but actors work
great when i use scala 2.7.x on android.  will 2.8.0, when it is
released, work as well as 2.7.x on android?

On Tue, Dec 1, 2009 at 10:56 PM, martin odersky <martin.odersky <at> epfl.ch> wrote:
> We just decided in the Scala meeting to keep Java 1.5 as not only the
> default, but the only version required by Scala 2.8. We will make use
> of dynamic class loading and reflection to load the real FJ  framework
> instead of its 1.5 backport or java.util.concurrent. This decision
> holds unless some unexpected problems come up with this dynamic
> loading scheme.
>
> Cheers
>
>  -- Martin
>

--

-- 
.......__o
.......\<,
....( )/ ( )...


Gmane