Anyone read the x10 specification yet?

[i30817]

Seems like a sweet, sweet language. I am especially impressed by array invariants (do disable bounds checking), immutable types, the forkjoin exception threading model and of course, closures (class invariants aka design by contract is not something i appreciate).

http://dist.codehaus.org/x10/documentation/languagespec/x10-175.pdf

http://docs.codehaus.org/display/XTENLANG/New+To+X10

[Abuse]

1st Paragraph, 3rd Sentence.

It is becoming increasingly difficult to mange chip power and
heat

Page 85 (I'm skimming  )

Example 11.13.1 The following statement checks if an index is in range
and throws an exception if not.
if (i < 0 || i > x.length)
throw new IndexOutOfBoundsException();

They should get someone to proof read 

[i30817]

Holy shit.

Invariant based overloading (pattern matching).

1   2   3   4   5   6   7   8   9   10   11

class Point(i: Int, j: Int) {...} class Line(s: Point, e: Point{self != i}) {   // m1: Both points lie in the right half of the plane  def draw(){s.i>= 0 && e.i >= 0} = {...}   // m2: Both points lie on the y-axis  def draw(){s.i== 0 && e.i == 0} = {...}   // m3: Both points lie in the top half of the plane  def draw(){s.j>= 0 && e.j >= 0} = {...}   // m4: The general method  def draw() = {...} }

Three different implementations are given for the draw method, one for
the case in which the line lies in the right half of the plane, one for the case
that the line lies on the y-axis and the third for the case that the line lies in
the top half of the plane.
Consider the invocation
     m: Line{s.i < 0} = ...
     m.draw();
This generates a compile time error because there is no applicable method definition.
Consider the invocation
     m: Line{s.i>=0 && s.j>=0 && e.i>=0 && e.j>=0} = ...
     m.draw();
This generates a compile time error because both m1 and m3 are applicable.
Consider the invocation
     m: Line{s.i>=0 && s.j>=0 && e.i>=0} = ...
     m.draw();
This does not generate any compile-time error since only m1 is applicable.

Games published by our own members! Check 'em out!

[swpalmer]

Wow!  That "Line" thing is a perfect example of over-complicating things when you are trying to do the opposite.

[princec]

I want BASIC. With classes. And global functions. And no public/private/protected modifiers. I think that should do the trick.

Cas