x10-core — List for X10 core design team

Re: [X10-core] plan for a X10 2.6.2 release

[David P G. <gr...@us...>]

The release is up at http://x10-lang.org/releases/x10-release-262.html.
I'll send an announcement next week.

--dave



From:	"David P Grove" <gr...@us...>
To:	X10 core design <x10...@li...>
Date:	01/04/2019 11:15 AM
Subject:	Re: [X10-core] plan for a X10 2.6.2 release



Thanks Mikio!

The full test suite for both Managed and Native X10 ran successfully last
night, so I believe we are in good shape to make a release. I will go ahead
with git tagging and building artifacts today.

--dave


Inactive hide details for Mikio Takeuchi ---01/04/2019 05:06:38 AM---Hi
Dave, Thank you for taking care of the new X10 release!Mikio Takeuchi
---01/04/2019 05:06:38 AM---Hi Dave, Thank you for taking care of the new
X10 release! I also spent some time

From: Mikio Takeuchi <mik...@gm...>
To: X10 core design <x10...@li...>
Date: 01/04/2019 05:06 AM
Subject: Re: [X10-core] plan for a X10 2.6.2 release



Hi Dave,

Thank you for taking care of the new X10 release!  I also spent some time
today and fixed the ManagedX10 build failure with Java11. With this change,
we will require Ant 1.10.2 or later to build X10 from source. I updated the
instruction on how to build X10 at the x10-lang web site. I also updated
ecj and hazelcast to the latest.

It is great if you can pick up my commits for the release.

-- Mikio


2019年1月4日(金) 6:44 David P Grove <gr...@us...>:
      I've spent a little time today and resolved the NativeX10 segfaults
      on MacOS 10.12/10.13 problem. We also have Mikio's work from last
      year to support Java9 with ManagedX10 that hasn't made it into a
      release yet.

      I propose to go ahead with a release of X10 (not X10DT) with
      pre-built packages for MacOS and Linux in addition to the source
      packages. (I don't have ready access to a Windows machine with the
      proper build environment. If anyone does and wants to build a
      pre-built Windows tar ball for the release let me know).

      I've kicked off a manual run of the full test suite on Linux to
      verify that the system is still sane. Assuming that goes ok, I would
      like to push out the release early next week.

      --dave

      _______________________________________________
      X10-core mailing list
      X10...@li...
      https://lists.sourceforge.net/lists/listinfo/x10-core
      _______________________________________________
      X10-core mailing list
      X10...@li...
      https://lists.sourceforge.net/lists/listinfo/x10-core




_______________________________________________
X10-core mailing list
X10...@li...
https://lists.sourceforge.net/lists/listinfo/x10-core

Re: [X10-core] plan for a X10 2.6.2 release

[David P G. <gr...@us...>]

Hi Krishna,

	The path forward would be to submit one or more pull requests to the
github project with the changes.  That will allow them to be reviewed and
hopefully merged. If we can get them merged in, then we could make a
subsequent release.

regards,

--dave



From:	"V. Krishna Nandivada" <nv...@cs...>
To:	X10 core design <x10...@li...>, David P Grove
            <gr...@us...>
Date:	01/04/2019 12:36 PM
Subject:	Re: [X10-core] plan for a X10 2.6.2 release



Hi Dave,

One of the issues we had found with X10 with distributed environment was
with multiple places - in this regard our recent paper in PACT 2018 (see
below) makes a big difference wherein we only copy the relevant data during
place change operations. And impact is huge. Here are the details of the
paper:

Optimizing Remote Data Transfers in X10. A Thangamani and V K Nandivada in
the proceedings of the Parallel Architectures and Compilation Techniques
(PACT), 2018. Artifact evaluated (Available, Customizable-reusable, Results
replicated).

I am thinking how we can push in the changes to a release.

Best,
Krishna.

      On 04-Jan-2019, at 10:15 AM, David P Grove <gr...@us...> wrote:



      Thanks Mikio!

      The full test suite for both Managed and Native X10 ran successfully
      last night, so I believe we are in good shape to make a release. I
      will go ahead with git tagging and building artifacts today.

      --dave


      Inactive hide details for Mikio Takeuchi ---01/04/2019 05:06:38
      AM---Hi Dave, Thank you for taking care of the new X10 release!Mikio
      Takeuchi ---01/04/2019 05:06:38 AM---Hi Dave, Thank you for taking
      care of the new X10 release! I also spent some time

      From: Mikio Takeuchi <mik...@gm...>
      To: X10 core design <x10...@li...>
      Date: 01/04/2019 05:06 AM
      Subject: Re: [X10-core] plan for a X10 2.6.2 release





      Hi Dave,

      Thank you for taking care of the new X10 release!  I also spent some
      time today and fixed the ManagedX10 build failure with Java11. With
      this change, we will require Ant 1.10.2 or later to build X10 from
      source. I updated the instruction on how to build X10 at the x10-lang
      web site. I also updated ecj and hazelcast to the latest.

      It is great if you can pick up my commits for the release.

      -- Mikio


      2019年1月4日(金) 6:44 David P Grove <gr...@us...>:
            I've spent a little time today and resolved the NativeX10
            segfaults on MacOS 10.12/10.13 problem. We also have Mikio's
            work from last year to support Java9 with ManagedX10 that
            hasn't made it into a release yet.

            I propose to go ahead with a release of X10 (not X10DT) with
            pre-built packages for MacOS and Linux in addition to the
            source packages. (I don't have ready access to a Windows
            machine with the proper build environment. If anyone does and
            wants to build a pre-built Windows tar ball for the release let
            me know).

            I've kicked off a manual run of the full test suite on Linux to
            verify that the system is still sane. Assuming that goes ok, I
            would like to push out the release early next week.

            --dave

            _______________________________________________
            X10-core mailing list
            X10...@li...
            https://lists.sourceforge.net/lists/listinfo/x10-core
            _______________________________________________
            X10-core mailing list
            X10...@li...
            https://lists.sourceforge.net/lists/listinfo/x10-core



      _______________________________________________
      X10-core mailing list
      X10...@li...
      https://lists.sourceforge.net/lists/listinfo/x10-core

Re: [X10-core] plan for a X10 2.6.2 release

[V. K. N. <nv...@cs...>]

Hi Dave,

One of the issues we had found with X10 with distributed environment was with multiple places - in this regard our recent paper in PACT 2018 (see below) makes a big difference wherein we only copy the relevant data during place change operations. And impact is huge. Here are the details of the paper:

Optimizing Remote Data Transfers in X10. A Thangamani and V K Nandivada in the proceedings of the Parallel Architectures and Compilation Techniques (PACT), 2018. Artifact evaluated (Available, Customizable-reusable, Results replicated).

I am thinking how we can push in the changes to a release.

Best,
Krishna.

> On 04-Jan-2019, at 10:15 AM, David P Grove <gr...@us...> wrote:
> 
> Thanks Mikio! 
> 
> The full test suite for both Managed and Native X10 ran successfully last night, so I believe we are in good shape to make a release. I will go ahead with git tagging and building artifacts today.
> 
> --dave
> 
> 
> Mikio Takeuchi ---01/04/2019 05:06:38 AM---Hi Dave, Thank you for taking care of the new X10 release! I also spent some time
> 
> From: Mikio Takeuchi <mik...@gm...>
> To: X10 core design <x10...@li...>
> Date: 01/04/2019 05:06 AM
> Subject: Re: [X10-core] plan for a X10 2.6.2 release
> 
> 
> 
> 
> Hi Dave,
> 
> Thank you for taking care of the new X10 release!  I also spent some time today and fixed the ManagedX10 build failure with Java11. With this change, we will require Ant 1.10.2 or later to build X10 from source. I updated the instruction on how to build X10 at the x10-lang web site. I also updated ecj and hazelcast to the latest.  
> 
> It is great if you can pick up my commits for the release.
> 
> -- Mikio
> 
> 
> 2019年1月4日(金) 6:44 David P Grove <gr...@us... <mailto:gr...@us...>>:
> I've spent a little time today and resolved the NativeX10 segfaults on MacOS 10.12/10.13 problem. We also have Mikio's work from last year to support Java9 with ManagedX10 that hasn't made it into a release yet.
> 
> I propose to go ahead with a release of X10 (not X10DT) with pre-built packages for MacOS and Linux in addition to the source packages. (I don't have ready access to a Windows machine with the proper build environment. If anyone does and wants to build a pre-built Windows tar ball for the release let me know). 
> 
> I've kicked off a manual run of the full test suite on Linux to verify that the system is still sane. Assuming that goes ok, I would like to push out the release early next week.
> 
> --dave
> 
> _______________________________________________
> X10-core mailing list
> X10...@li... <mailto:X10...@li...>
> https://lists.sourceforge.net/lists/listinfo/x10-core <https://lists.sourceforge.net/lists/listinfo/x10-core>_______________________________________________
> X10-core mailing list
> X10...@li...
> https://lists.sourceforge.net/lists/listinfo/x10-core <https://lists.sourceforge.net/lists/listinfo/x10-core>
> 
> 
> 
> _______________________________________________
> X10-core mailing list
> X10...@li...
> https://lists.sourceforge.net/lists/listinfo/x10-core

Re: [X10-core] plan for a X10 2.6.2 release

[David P G. <gr...@us...>]

Thanks Mikio!

The full test suite for both Managed and Native X10 ran successfully last
night, so I believe we are in good shape to make a release.  I will go
ahead with git tagging and building artifacts today.

--dave




From:	Mikio Takeuchi <mik...@gm...>
To:	X10 core design <x10...@li...>
Date:	01/04/2019 05:06 AM
Subject:	Re: [X10-core] plan for a X10 2.6.2 release



Hi Dave,

Thank you for taking care of the new X10 release!  I also spent some time
today and fixed the ManagedX10 build failure with Java11. With this change,
we will require Ant 1.10.2 or later to build X10 from source. I updated the
instruction on how to build X10 at the x10-lang web site. I also updated
ecj and hazelcast to the latest.

It is great if you can pick up my commits for the release.

-- Mikio


2019年1月4日(金) 6:44 David P Grove <gr...@us...>:
  I've spent a little time today and resolved the NativeX10 segfaults on
  MacOS 10.12/10.13 problem. We also have Mikio's work from last year to
  support Java9 with ManagedX10 that hasn't made it into a release yet.

  I propose to go ahead with a release of X10 (not X10DT) with pre-built
  packages for MacOS and Linux in addition to the source packages. (I don't
  have ready access to a Windows machine with the proper build environment.
  If anyone does and wants to build a pre-built Windows tar ball for the
  release let me know).

  I've kicked off a manual run of the full test suite on Linux to verify
  that the system is still sane. Assuming that goes ok, I would like to
  push out the release early next week.

  --dave

  _______________________________________________
  X10-core mailing list
  X10...@li...
  https://lists.sourceforge.net/lists/listinfo/x10-core
  _______________________________________________
  X10-core mailing list
  X10...@li...
  https://lists.sourceforge.net/lists/listinfo/x10-core

Re: [X10-core] plan for a X10 2.6.2 release

[Mikio T. <mik...@gm...>]

Hi Dave,

Thank you for taking care of the new X10 release!  I also spent some time
today and fixed the ManagedX10 build failure with Java11. With this change,
we will require Ant 1.10.2 or later to build X10 from source. I updated the
instruction on how to build X10 at the x10-lang web site. I also updated
ecj and hazelcast to the latest.

It is great if you can pick up my commits for the release.

-- Mikio


2019年1月4日(金) 6:44 David P Grove <gr...@us...>:

> I've spent a little time today and resolved the NativeX10 segfaults on
> MacOS 10.12/10.13 problem. We also have Mikio's work from last year to
> support Java9 with ManagedX10 that hasn't made it into a release yet.
>
> I propose to go ahead with a release of X10 (not X10DT) with pre-built
> packages for MacOS and Linux in addition to the source packages. (I don't
> have ready access to a Windows machine with the proper build environment.
> If anyone does and wants to build a pre-built Windows tar ball for the
> release let me know).
>
> I've kicked off a manual run of the full test suite on Linux to verify
> that the system is still sane. Assuming that goes ok, I would like to push
> out the release early next week.
>
> --dave
>
> _______________________________________________
> X10-core mailing list
> X10...@li...
> https://lists.sourceforge.net/lists/listinfo/x10-core
>

[X10-core] plan for a X10 2.6.2 release

[David P G. <gr...@us...>]

I've spent a little time today and resolved the NativeX10 segfaults on
MacOS 10.12/10.13 problem.  We also have Mikio's work from last year to
support Java9 with ManagedX10 that hasn't made it into a release yet.

I propose to go ahead with a release of X10 (not X10DT) with pre-built
packages for MacOS and Linux in addition to the source packages.  (I don't
have ready access to a Windows machine with the proper build environment.
If anyone does and wants to build a pre-built Windows tar ball for the
release let me know).

I've kicked off a manual run of the full test suite on Linux to verify that
the system is still sane.  Assuming that goes ok, I would like to push out
the release early next week.

--dave

[X10-core] Constrained types in Stan

[Vijay S. <vi...@sa...>]

Interesting that Stan, a C++ based probabilistic programing language, 
implemented a version of constrained types.

Stan: A Probabilistic Programming Language

http://www.stat.columbia.edu/~gelman/research/published/stan-paper-revision-feb2015.pdf

-----

Variables may be declared with constraints. The constraints have 
different effects depending on the block in which the variable is declared.

Integer and real types may be provided with lower bounds, upper bounds, 
or both. This includes the types used in arrays, and the real types used 
in vectors and matrices.

Vector types may be constrained to be unit simplexes (all entries 
non-negative and summing to 1), unit length vectors (sum of squares is 
1), or ordered (entries are in ascending order), positive ordered 
(entries in ascending order, all non-negative), using the types 
simplex[K], unit_vector[K], ordered[K], or positive_ordered[K], where K 
is the size of the vector.

Matrices may be constrained to be covariance matrices (symmetric, 
positive definite) or corre- lation matrices (symmetric, positive 
definite, unit diagonal), using the types cov_matrix[K] and corr_matrix[K].

-----

[X10-core] JIRA / GitHub integration for X10 project

[David P G. <gr...@us...>]

I've enabled 'smart commit' linking between all the X10 GitHub repositories
and our JIRA instance.

What this means is that if you mention a JIRA issue key (eg XTENLANG-1234)
in a git commit message the changeset will automatically be linked to the
JIRA issue.

You can also give commands in the commit message (see
https://confluence.atlassian.com/bitbucket/processing-jira-issues-with-smart-commit-messages-298979931.html
) that will cause actions to automatically happen in JIRA; for example
resolving the issue.

Right now, the system is processing the project history of all commits and
creating all of the links between JIRA issues and changesets.  Should be
caught up by late tonight.

--dave

Re: [X10-core] contemplating conversion from svn to git

[Andreas Z. <zw...@ki...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 22.07.2015 um 03:30 schrieb Vijay Saraswat:
> We believe we will be able to carry history over.
> 
> On 7/21/15 9:18 PM, Bard Bloom wrote: ...
>> How much information will you lose moving to git? Or does the 
>> translation somehow carry history onwards?

git-svn is a nice svn client and also does the conversion. So, you can
easily try out git without breaking anything. You could also start
with a git mirror at first and keep the svn.

Nevertheless, there are some pitfalls for a "great" conversion,
though. For example, svn has usernames, where git uses name+email
pairs. It could be a good idea to "enrich" or "normalize" git history
with a few scripts after the final conversion. Since changing history
in git is not something you do in a public repository, it needs to be
done before it goes live.

We also split the One Big Svn Repo into multiple git repos, which hold
together via git-submodule. I'm not sure if that would be a good idea
for X10, though.

In libfirm [0], the last svn revision r28454 is now git commit ed85eaaf.

[0] http://pp.ipd.kit.edu/git/libfirm/
- -- 
Andreas Zwinkau

 KIT  IPD Snelting
 Web: http://pp.ipd.kit.edu/personhp/andreas_zwinkau.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVugc6AAoJEKm3M8a3pi2iq1cH/2ij8tvKmJXCiHa8uNQSWyK1
oN9FUcnnMNd0NtsjU8ogrAsclFuWmXNKwEHK/KVPDhh04zkEAQzQdrErG7NYlVZi
t8R92TXspvwDEgcc5dzZKrO0CNiBncdIcd34c/WVTToGeSSg2Selu6VfwPJ8rLqY
IB+KmKxl01vrmPJen2Gh62Ue0DzaJUwHpm7TW8kHx7pjQ6OX/pA+orjPPMPl+xGh
t0AUoIgeyWwjvg3CbilpBUWnaWRp5g9RFRQX9lMr5asKH1tEju/CDLIG08oEg9a1
6WEPCIQq0VXfoBPxkdlkMWqpL7UvoqZoPghGceU6FDxxmTtWW0J6sAs9/UCgnW0=
=Vle6
-----END PGP SIGNATURE-----

[X10-core] AUTO: Stephen Fink/Watson/IBM is out of the office (returning 07/27/2015)

[Stephen F. <sj...@us...>]

I am out of the office until 07/27/2015.

Hi,

I will be on vacation and unreachable from Thursday, July 16, until Monday
July 27.

For management-related issues, please contact Mike Hind or Matt Arnold
during my absence.   For whisk-related project issues, please contact
Rodric Rabbah.

SJF


Note: This is an automated response to your message  "[X10-core]
contemplating conversion from svn to git" sent on 07/21/2015 10:39:43 AM.

This is the only notification you will receive while this person is away.

Re: [X10-core] contemplating conversion from svn to git

[Vijay S. <vi...@sa...>]

We believe we will be able to carry history over.

On 7/21/15 9:18 PM, Bard Bloom wrote:
...
> How much information will you lose moving to git? Or does the 
> translation somehow carry history onwards?
>

Re: [X10-core] contemplating conversion from svn to git

[Bard B. <bar...@gm...>]

Not that I particularly give a shit, but one important feature of source
code control is that it holds a great deal of history.  I have certainly
found this endlessly helpful doing archaeology in odd-looking design
decisions in old Google code.  How much information will you lose moving to
git?  Or does the translation somehow carry history onwards?

On Tue, Jul 21, 2015 at 10:39 AM, David P Grove <gr...@us...> wrote:

> We're contemplating converting the X10 project from svn to git for source
> code control.  If anyone has any reservations about this conversion, please
> comment.
>
> We couldn't start the conversion until after sourceforge svn gets back
> online, so this at earliest we would look to be converting next week.
>
> --dave
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> X10-core mailing list
> X10...@li...
> https://lists.sourceforge.net/lists/listinfo/x10-core
>
>

[X10-core] contemplating conversion from svn to git

[David P G. <gr...@us...>]

We're contemplating converting the X10 project from svn to git for source
code control.  If anyone has any reservations about this conversion, please
comment.

We couldn't start the conversion until after sourceforge svn gets back
online, so this at earliest we would look to be converting next week.

--dave

[X10-core] migration of X10 issue tracking software (JIRA) to new hosting site

[David P G. <gr...@us...>]

Due to the approaching shutdown of Codehaus.org at the end of April,  we
have migrated the JIRA used for X10 project issue tracking to a new
location: https://xtenlang.atlassian.net/projects/XTENLANG.


The new JIRA is now fully operational and should be used for all X10
issues.


Userids were migrated from the old JIRA at Codehaus to the new one, but for
security reasons passwords were not migrated.  If you had a userid in the
old JIRA, please use the password reset mechanism to set a password in the
new X10 JIRA instance.  If that doesn't work, please contact David Grove (
gr...@us...) to make sure your userid in the new JIRA is associated
with the correct email account to enable the password reset to work.


thanks,


--dave

Re: [X10-core] GlobalRef confused with a constructor

[Sara S. <sar...@gm...>]

Thanks a lot Mikio for informing me with this work around that solved my
problem.

Best Regards,
Sara


On Fri, May 16, 2014 at 6:09 PM, Mikio Takeuchi <mik...@gm...>wrote:

> Hi,
>
> I understand the problem.
> It looks like the compiler front-end is not strong enough to understand
> that this.parentEntryGR at current place is same as this.parentEntryGR at
> remote place.
> I am not sure but it may due to the field is mutable (var) rather than
> val.
> GlobalRef can be dereferenced only at the home place. Making it explicit
> by using a local variable of different name, we can work around the issue.
>
> -- Mikio
>
> package x10.lang;
>
> public class Entry {
>     private var name:String;
>     private var parentEntryGR:GlobalRef[Entry];
>
>     //constructor for the parent:only the parent has a name
>     public def this(name:String) {
>
>         this.name = name;
>     }
>
>     //constructor for the children, just pointing at the parent entry
>     public def this(parentEntry:GlobalRef[Entry]) {
>         this.parentEntryGR = parentEntry;
>     }
>
>     public def printParentEntryName() {
>         val parentGR = parentEntryGR;
>         at (parentGR) {
>             Console.OUT.println(parentGR().name);
>         }
>         // or even better
>         //Console.OUT.println(parentEntryGR.getLocalOrCopy().name);
>
>     }
>
>     public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
>     public def setParentEntryGR(parentGR:GlobalRef[Entry])
> {this.parentEntryGR = parentGR;}
> }
>
>
>
> 2014-05-16 15:16 GMT+09:00 Sara Salem <sar...@gm...>:
>
> Thanks a lot Mikio, but I'm afraid that this doesn't solve my problem. I
>> get the same result as you when I use x10c++ to compile that code, but my
>> problem is that when I add the Entry class to X10's runtime code in this
>> path (<X10-SRC-DIR>/x10.runtime/src-x10/x10/lang/Entry.x10) and then try
>> to compile X10's source by these commands (*cd **<X10-SRC-DIR>/x10.dist*
>> then  *ant dist*) I get the mentioned error.
>>
>> Thank you,
>> Sara
>>
>>
>> On Fri, May 16, 2014 at 2:27 PM, Mikio Takeuchi <mik...@gm...
>> > wrote:
>>
>>> Hi,
>>>
>>> You may need to make Entry class public so that it can be accessible
>>> from other packages.
>>> Following is the result with trunk r27694.
>>>
>>> -- Mikio
>>>
>>> [mtake@mtakex10 sara]$ cat x10/lang/Entry.x10
>>> package x10.lang;
>>>
>>> public class Entry {
>>>
>>>     private var name:String;
>>>     private var parentEntryGR:GlobalRef[Entry];
>>>
>>>     //constructor for the parent:only the parent has a name
>>>     public def this(var name:String) {
>>>         this.name = name;
>>>     }
>>>
>>>     //constructor for the children, just pointing at the parent entry
>>>     public def this(parentEntry:GlobalRef[Entry]) {
>>>         this.parentEntryGR = parentEntry;
>>>     }
>>>
>>>     public def printParentEntryName() {
>>>         at (parentEntryGR) {
>>>             Console.OUT.println(parentEntryGR().name);   /*Error: Method
>>> or static constructor not found for given call.*/
>>>         }
>>>     }
>>>
>>>     public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
>>>     public def setParentEntryGR(var parentGR:GlobalRef[Entry])
>>> {this.parentEntryGR = parentGR;}
>>> }
>>> [mtake@mtakex10 sara]$ cat TestGlobalRef.x10
>>>
>>> //Test class
>>> public class TestGlobalRef {
>>>     public static def main(val args:Rail[String]) {
>>>         //create the parent entry at place 0
>>>         val parentEnt:Entry = new Entry("parent name");
>>>         val parentEntGR = GlobalRef[Entry](parentEnt);
>>>         parentEnt.setParentEntryGR(parentEntGR);
>>>         for (p in Place.places()) {
>>>             at (p) {
>>>                 val entry:Entry;
>>>                 if (p.id != parentEntGR.home.id)
>>>                     entry = new Entry(parentEntGR); //create children
>>> Entries on other places
>>>                 else
>>>                     entry = at (parentEntGR) {parentEntGR()};
>>>                 entry.printParentEntryName();
>>>             }
>>>         }
>>>     }
>>> }
>>> [mtake@mtakex10 sara]$ x10c TestGlobalRef.x10
>>> x10c: 1 dynamically checked calls or field accesses, run with
>>> -VERBOSE_CHECKS for more details.
>>> [mtake@mtakex10 sara]$ x10c++ TestGlobalRef.x10
>>> x10c++: 1 dynamically checked calls or field accesses, run with
>>> -VERBOSE_CHECKS for more details.
>>> [mtake@mtakex10 sara]$
>>>
>>>
>>> 2014-05-16 12:03 GMT+09:00 Sara Salem <sar...@gm...>:
>>>
>>>>  Hello,
>>>>   I have a problem with the below Entry class. It compiles correctly
>>>> using x10c++, but when I add it to the x10.lang package
>>>> (<X10-SRC-DIR>/x10.runtime/src-x10/x10/lang) and try to compile X10 using *ant
>>>> dist*, I get an error at the statement when I use the GlobalRef to
>>>> access a remote Entry object. *The error is: Method or static
>>>> constructor not found for given call.*
>>>>
>>>> Below is the Entry class, and a main method describing how I use it.
>>>> How can I fix this error to get the class compiling as part of x10.lang
>>>> package?
>>>>
>>>> class Entry{
>>>>     private var name:String;
>>>>     private var parentEntryGR:GlobalRef[Entry];
>>>>
>>>>     //constructor for the parent:only the parent has a name
>>>>     public def this(var name:String){
>>>>     this.name = name;
>>>>     }
>>>>
>>>>     //constructor for the children, just pointing at the parent entry
>>>>     public def this(parentEntry:GlobalRef[Entry]){
>>>>         this.parentEntryGR = parentEntry;
>>>>     }
>>>>
>>>>     public def printParentEntryName(){
>>>>     at(parentEntryGR)
>>>>     {
>>>>     Console.OUT.println(parentEntryGR().name);   /*Error: Method or
>>>> static constructor not found for given call.*/
>>>>     }
>>>>     }
>>>>     public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
>>>>     public def setParentEntryGR(var parentGR:GlobalRef[Entry])
>>>> {this.parentEntryGR = parentGR;}
>>>>
>>>> }
>>>>
>>>>
>>>> //Test class
>>>> public class TestGlobalRef {
>>>>     public static def main(val args:Rail[String]){
>>>>         //create the parent entry at place 0
>>>>         val parentEnt:Entry = new Entry("parent name");
>>>>         val parentEntGR = GlobalRef[Entry](parentEnt);
>>>>         parentEnt.setParentEntryGR(parentEntGR);
>>>>
>>>>         for (p in Place.places())
>>>>         {
>>>>             at(p)
>>>>             {
>>>>                 val entry:Entry;
>>>>                 if (p.id != parentEntGR.home.id)
>>>>                     entry = new Entry(parentEntGR); //create children
>>>> Entries on other places
>>>>                 else
>>>>                 entry = at (parentEntGR) {parentEntGR()};
>>>>
>>>>                 entry.printParentEntryName();
>>>>             }
>>>>         }
>>>>     }
>>>> }
>>>>
>>>> Thank you,
>>>> Sara
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>>>> Instantly run your Selenium tests across 300+ browser/OS combos.
>>>> Get unparalleled scalability from the best Selenium testing platform
>>>> available
>>>> Simple to use. Nothing to install. Get started now for free."
>>>> http://p.sf.net/sfu/SauceLabs
>>>> _______________________________________________
>>>> X10-core mailing list
>>>> X10...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/x10-core
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>>> Instantly run your Selenium tests across 300+ browser/OS combos.
>>> Get unparalleled scalability from the best Selenium testing platform
>>> available
>>> Simple to use. Nothing to install. Get started now for free."
>>> http://p.sf.net/sfu/SauceLabs
>>> _______________________________________________
>>> X10-core mailing list
>>> X10...@li...
>>> https://lists.sourceforge.net/lists/listinfo/x10-core
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.
>> Get unparalleled scalability from the best Selenium testing platform
>> available
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs
>> _______________________________________________
>> X10-core mailing list
>> X10...@li...
>> https://lists.sourceforge.net/lists/listinfo/x10-core
>>
>>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> X10-core mailing list
> X10...@li...
> https://lists.sourceforge.net/lists/listinfo/x10-core
>
>

Re: [X10-core] GlobalRef confused with a constructor

[Mikio T. <mik...@gm...>]

Hi,

I understand the problem.
It looks like the compiler front-end is not strong enough to understand
that this.parentEntryGR at current place is same as this.parentEntryGR at
remote place.
I am not sure but it may due to the field is mutable (var) rather than val.
GlobalRef can be dereferenced only at the home place. Making it explicit by
using a local variable of different name, we can work around the issue.

-- Mikio

package x10.lang;

public class Entry {
    private var name:String;
    private var parentEntryGR:GlobalRef[Entry];

    //constructor for the parent:only the parent has a name
    public def this(name:String) {
        this.name = name;
    }

    //constructor for the children, just pointing at the parent entry
    public def this(parentEntry:GlobalRef[Entry]) {
        this.parentEntryGR = parentEntry;
    }

    public def printParentEntryName() {
        val parentGR = parentEntryGR;
        at (parentGR) {
            Console.OUT.println(parentGR().name);
        }
        // or even better
        //Console.OUT.println(parentEntryGR.getLocalOrCopy().name);
    }

    public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
    public def setParentEntryGR(parentGR:GlobalRef[Entry])
{this.parentEntryGR = parentGR;}
}



2014-05-16 15:16 GMT+09:00 Sara Salem <sar...@gm...>:

> Thanks a lot Mikio, but I'm afraid that this doesn't solve my problem. I
> get the same result as you when I use x10c++ to compile that code, but my
> problem is that when I add the Entry class to X10's runtime code in this
> path (<X10-SRC-DIR>/x10.runtime/src-x10/x10/lang/Entry.x10) and then try
> to compile X10's source by these commands (*cd **<X10-SRC-DIR>/x10.dist*
> then  *ant dist*) I get the mentioned error.
>
> Thank you,
> Sara
>
>
> On Fri, May 16, 2014 at 2:27 PM, Mikio Takeuchi <mik...@gm...>wrote:
>
>> Hi,
>>
>> You may need to make Entry class public so that it can be accessible from
>> other packages.
>> Following is the result with trunk r27694.
>>
>> -- Mikio
>>
>> [mtake@mtakex10 sara]$ cat x10/lang/Entry.x10
>> package x10.lang;
>>
>> public class Entry {
>>
>>     private var name:String;
>>     private var parentEntryGR:GlobalRef[Entry];
>>
>>     //constructor for the parent:only the parent has a name
>>     public def this(var name:String) {
>>         this.name = name;
>>     }
>>
>>     //constructor for the children, just pointing at the parent entry
>>     public def this(parentEntry:GlobalRef[Entry]) {
>>         this.parentEntryGR = parentEntry;
>>     }
>>
>>     public def printParentEntryName() {
>>         at (parentEntryGR) {
>>             Console.OUT.println(parentEntryGR().name);   /*Error: Method
>> or static constructor not found for given call.*/
>>         }
>>     }
>>
>>     public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
>>     public def setParentEntryGR(var parentGR:GlobalRef[Entry])
>> {this.parentEntryGR = parentGR;}
>> }
>> [mtake@mtakex10 sara]$ cat TestGlobalRef.x10
>>
>> //Test class
>> public class TestGlobalRef {
>>     public static def main(val args:Rail[String]) {
>>         //create the parent entry at place 0
>>         val parentEnt:Entry = new Entry("parent name");
>>         val parentEntGR = GlobalRef[Entry](parentEnt);
>>         parentEnt.setParentEntryGR(parentEntGR);
>>         for (p in Place.places()) {
>>             at (p) {
>>                 val entry:Entry;
>>                 if (p.id != parentEntGR.home.id)
>>                     entry = new Entry(parentEntGR); //create children
>> Entries on other places
>>                 else
>>                     entry = at (parentEntGR) {parentEntGR()};
>>                 entry.printParentEntryName();
>>             }
>>         }
>>     }
>> }
>> [mtake@mtakex10 sara]$ x10c TestGlobalRef.x10
>> x10c: 1 dynamically checked calls or field accesses, run with
>> -VERBOSE_CHECKS for more details.
>> [mtake@mtakex10 sara]$ x10c++ TestGlobalRef.x10
>> x10c++: 1 dynamically checked calls or field accesses, run with
>> -VERBOSE_CHECKS for more details.
>> [mtake@mtakex10 sara]$
>>
>>
>> 2014-05-16 12:03 GMT+09:00 Sara Salem <sar...@gm...>:
>>
>>>  Hello,
>>>   I have a problem with the below Entry class. It compiles correctly
>>> using x10c++, but when I add it to the x10.lang package
>>> (<X10-SRC-DIR>/x10.runtime/src-x10/x10/lang) and try to compile X10 using *ant
>>> dist*, I get an error at the statement when I use the GlobalRef to
>>> access a remote Entry object. *The error is: Method or static
>>> constructor not found for given call.*
>>>
>>> Below is the Entry class, and a main method describing how I use it.
>>> How can I fix this error to get the class compiling as part of x10.lang
>>> package?
>>>
>>> class Entry{
>>>     private var name:String;
>>>     private var parentEntryGR:GlobalRef[Entry];
>>>
>>>     //constructor for the parent:only the parent has a name
>>>     public def this(var name:String){
>>>     this.name = name;
>>>     }
>>>
>>>     //constructor for the children, just pointing at the parent entry
>>>     public def this(parentEntry:GlobalRef[Entry]){
>>>         this.parentEntryGR = parentEntry;
>>>     }
>>>
>>>     public def printParentEntryName(){
>>>     at(parentEntryGR)
>>>     {
>>>     Console.OUT.println(parentEntryGR().name);   /*Error: Method or
>>> static constructor not found for given call.*/
>>>     }
>>>     }
>>>     public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
>>>     public def setParentEntryGR(var parentGR:GlobalRef[Entry])
>>> {this.parentEntryGR = parentGR;}
>>>
>>> }
>>>
>>>
>>> //Test class
>>> public class TestGlobalRef {
>>>     public static def main(val args:Rail[String]){
>>>         //create the parent entry at place 0
>>>         val parentEnt:Entry = new Entry("parent name");
>>>         val parentEntGR = GlobalRef[Entry](parentEnt);
>>>         parentEnt.setParentEntryGR(parentEntGR);
>>>
>>>         for (p in Place.places())
>>>         {
>>>             at(p)
>>>             {
>>>                 val entry:Entry;
>>>                 if (p.id != parentEntGR.home.id)
>>>                     entry = new Entry(parentEntGR); //create children
>>> Entries on other places
>>>                 else
>>>                 entry = at (parentEntGR) {parentEntGR()};
>>>
>>>                 entry.printParentEntryName();
>>>             }
>>>         }
>>>     }
>>> }
>>>
>>> Thank you,
>>> Sara
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>>> Instantly run your Selenium tests across 300+ browser/OS combos.
>>> Get unparalleled scalability from the best Selenium testing platform
>>> available
>>> Simple to use. Nothing to install. Get started now for free."
>>> http://p.sf.net/sfu/SauceLabs
>>> _______________________________________________
>>> X10-core mailing list
>>> X10...@li...
>>> https://lists.sourceforge.net/lists/listinfo/x10-core
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.
>> Get unparalleled scalability from the best Selenium testing platform
>> available
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs
>> _______________________________________________
>> X10-core mailing list
>> X10...@li...
>> https://lists.sourceforge.net/lists/listinfo/x10-core
>>
>>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> X10-core mailing list
> X10...@li...
> https://lists.sourceforge.net/lists/listinfo/x10-core
>
>

Re: [X10-core] GlobalRef confused with a constructor

[Sara S. <sar...@gm...>]

Thanks a lot Mikio, but I'm afraid that this doesn't solve my problem. I
get the same result as you when I use x10c++ to compile that code, but my
problem is that when I add the Entry class to X10's runtime code in this
path (<X10-SRC-DIR>/x10.runtime/src-x10/x10/lang/Entry.x10) and then try to
compile X10's source by these commands (*cd **<X10-SRC-DIR>/x10.dist*  then
 *ant dist*) I get the mentioned error.

Thank you,
Sara


On Fri, May 16, 2014 at 2:27 PM, Mikio Takeuchi <mik...@gm...>wrote:

> Hi,
>
> You may need to make Entry class public so that it can be accessible from
> other packages.
> Following is the result with trunk r27694.
>
> -- Mikio
>
> [mtake@mtakex10 sara]$ cat x10/lang/Entry.x10
> package x10.lang;
>
> public class Entry {
>
>     private var name:String;
>     private var parentEntryGR:GlobalRef[Entry];
>
>     //constructor for the parent:only the parent has a name
>     public def this(var name:String) {
>         this.name = name;
>     }
>
>     //constructor for the children, just pointing at the parent entry
>     public def this(parentEntry:GlobalRef[Entry]) {
>         this.parentEntryGR = parentEntry;
>     }
>
>     public def printParentEntryName() {
>         at (parentEntryGR) {
>             Console.OUT.println(parentEntryGR().name);   /*Error: Method
> or static constructor not found for given call.*/
>         }
>     }
>
>     public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
>     public def setParentEntryGR(var parentGR:GlobalRef[Entry])
> {this.parentEntryGR = parentGR;}
> }
> [mtake@mtakex10 sara]$ cat TestGlobalRef.x10
>
> //Test class
> public class TestGlobalRef {
>     public static def main(val args:Rail[String]) {
>         //create the parent entry at place 0
>         val parentEnt:Entry = new Entry("parent name");
>         val parentEntGR = GlobalRef[Entry](parentEnt);
>         parentEnt.setParentEntryGR(parentEntGR);
>         for (p in Place.places()) {
>             at (p) {
>                 val entry:Entry;
>                 if (p.id != parentEntGR.home.id)
>                     entry = new Entry(parentEntGR); //create children
> Entries on other places
>                 else
>                     entry = at (parentEntGR) {parentEntGR()};
>                 entry.printParentEntryName();
>             }
>         }
>     }
> }
> [mtake@mtakex10 sara]$ x10c TestGlobalRef.x10
> x10c: 1 dynamically checked calls or field accesses, run with
> -VERBOSE_CHECKS for more details.
> [mtake@mtakex10 sara]$ x10c++ TestGlobalRef.x10
> x10c++: 1 dynamically checked calls or field accesses, run with
> -VERBOSE_CHECKS for more details.
> [mtake@mtakex10 sara]$
>
>
> 2014-05-16 12:03 GMT+09:00 Sara Salem <sar...@gm...>:
>
>> Hello,
>>   I have a problem with the below Entry class. It compiles correctly
>> using x10c++, but when I add it to the x10.lang package
>> (<X10-SRC-DIR>/x10.runtime/src-x10/x10/lang) and try to compile X10 using *ant
>> dist*, I get an error at the statement when I use the GlobalRef to
>> access a remote Entry object. *The error is: Method or static
>> constructor not found for given call.*
>>
>> Below is the Entry class, and a main method describing how I use it.
>> How can I fix this error to get the class compiling as part of x10.lang
>> package?
>>
>> class Entry{
>>     private var name:String;
>>     private var parentEntryGR:GlobalRef[Entry];
>>
>>     //constructor for the parent:only the parent has a name
>>     public def this(var name:String){
>>     this.name = name;
>>     }
>>
>>     //constructor for the children, just pointing at the parent entry
>>     public def this(parentEntry:GlobalRef[Entry]){
>>         this.parentEntryGR = parentEntry;
>>     }
>>
>>     public def printParentEntryName(){
>>     at(parentEntryGR)
>>     {
>>     Console.OUT.println(parentEntryGR().name);   /*Error: Method or
>> static constructor not found for given call.*/
>>     }
>>     }
>>     public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
>>     public def setParentEntryGR(var parentGR:GlobalRef[Entry])
>> {this.parentEntryGR = parentGR;}
>>
>> }
>>
>>
>> //Test class
>> public class TestGlobalRef {
>>     public static def main(val args:Rail[String]){
>>         //create the parent entry at place 0
>>         val parentEnt:Entry = new Entry("parent name");
>>         val parentEntGR = GlobalRef[Entry](parentEnt);
>>         parentEnt.setParentEntryGR(parentEntGR);
>>
>>         for (p in Place.places())
>>         {
>>             at(p)
>>             {
>>                 val entry:Entry;
>>                 if (p.id != parentEntGR.home.id)
>>                     entry = new Entry(parentEntGR); //create children
>> Entries on other places
>>                 else
>>                 entry = at (parentEntGR) {parentEntGR()};
>>
>>                 entry.printParentEntryName();
>>             }
>>         }
>>     }
>> }
>>
>> Thank you,
>> Sara
>>
>>
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.
>> Get unparalleled scalability from the best Selenium testing platform
>> available
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs
>> _______________________________________________
>> X10-core mailing list
>> X10...@li...
>> https://lists.sourceforge.net/lists/listinfo/x10-core
>>
>>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> X10-core mailing list
> X10...@li...
> https://lists.sourceforge.net/lists/listinfo/x10-core
>
>

Re: [X10-core] GlobalRef confused with a constructor

[Mikio T. <mik...@gm...>]

Hi,

You may need to make Entry class public so that it can be accessible from
other packages.
Following is the result with trunk r27694.

-- Mikio

[mtake@mtakex10 sara]$ cat x10/lang/Entry.x10
package x10.lang;

public class Entry {
    private var name:String;
    private var parentEntryGR:GlobalRef[Entry];

    //constructor for the parent:only the parent has a name
    public def this(var name:String) {
        this.name = name;
    }

    //constructor for the children, just pointing at the parent entry
    public def this(parentEntry:GlobalRef[Entry]) {
        this.parentEntryGR = parentEntry;
    }

    public def printParentEntryName() {
        at (parentEntryGR) {
            Console.OUT.println(parentEntryGR().name);   /*Error: Method or
static constructor not found for given call.*/
        }
    }

    public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
    public def setParentEntryGR(var parentGR:GlobalRef[Entry])
{this.parentEntryGR = parentGR;}
}
[mtake@mtakex10 sara]$ cat TestGlobalRef.x10
//Test class
public class TestGlobalRef {
    public static def main(val args:Rail[String]) {
        //create the parent entry at place 0
        val parentEnt:Entry = new Entry("parent name");
        val parentEntGR = GlobalRef[Entry](parentEnt);
        parentEnt.setParentEntryGR(parentEntGR);
        for (p in Place.places()) {
            at (p) {
                val entry:Entry;
                if (p.id != parentEntGR.home.id)
                    entry = new Entry(parentEntGR); //create children
Entries on other places
                else
                    entry = at (parentEntGR) {parentEntGR()};
                entry.printParentEntryName();
            }
        }
    }
}
[mtake@mtakex10 sara]$ x10c TestGlobalRef.x10
x10c: 1 dynamically checked calls or field accesses, run with
-VERBOSE_CHECKS for more details.
[mtake@mtakex10 sara]$ x10c++ TestGlobalRef.x10
x10c++: 1 dynamically checked calls or field accesses, run with
-VERBOSE_CHECKS for more details.
[mtake@mtakex10 sara]$


2014-05-16 12:03 GMT+09:00 Sara Salem <sar...@gm...>:

> Hello,
>   I have a problem with the below Entry class. It compiles correctly using
> x10c++, but when I add it to the x10.lang package
> (<X10-SRC-DIR>/x10.runtime/src-x10/x10/lang) and try to compile X10 using *ant
> dist*, I get an error at the statement when I use the GlobalRef to access
> a remote Entry object. *The error is: Method or static constructor not
> found for given call.*
>
> Below is the Entry class, and a main method describing how I use it.
> How can I fix this error to get the class compiling as part of x10.lang
> package?
>
> class Entry{
>     private var name:String;
>     private var parentEntryGR:GlobalRef[Entry];
>
>     //constructor for the parent:only the parent has a name
>     public def this(var name:String){
>     this.name = name;
>     }
>
>     //constructor for the children, just pointing at the parent entry
>     public def this(parentEntry:GlobalRef[Entry]){
>         this.parentEntryGR = parentEntry;
>     }
>
>     public def printParentEntryName(){
>     at(parentEntryGR)
>     {
>     Console.OUT.println(parentEntryGR().name);   /*Error: Method or
> static constructor not found for given call.*/
>     }
>     }
>     public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
>     public def setParentEntryGR(var parentGR:GlobalRef[Entry])
> {this.parentEntryGR = parentGR;}
>
> }
>
>
> //Test class
> public class TestGlobalRef {
>     public static def main(val args:Rail[String]){
>         //create the parent entry at place 0
>         val parentEnt:Entry = new Entry("parent name");
>         val parentEntGR = GlobalRef[Entry](parentEnt);
>         parentEnt.setParentEntryGR(parentEntGR);
>
>         for (p in Place.places())
>         {
>             at(p)
>             {
>                 val entry:Entry;
>                 if (p.id != parentEntGR.home.id)
>                     entry = new Entry(parentEntGR); //create children
> Entries on other places
>                 else
>                 entry = at (parentEntGR) {parentEntGR()};
>
>                 entry.printParentEntryName();
>             }
>         }
>     }
> }
>
> Thank you,
> Sara
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> X10-core mailing list
> X10...@li...
> https://lists.sourceforge.net/lists/listinfo/x10-core
>
>

[X10-core] GlobalRef confused with a constructor

[Sara S. <sar...@gm...>]

Hello,
  I have a problem with the below Entry class. It compiles correctly using
x10c++, but when I add it to the x10.lang package
(<X10-SRC-DIR>/x10.runtime/src-x10/x10/lang) and try to compile X10 using *ant
dist*, I get an error at the statement when I use the GlobalRef to access a
remote Entry object. *The error is: Method or static constructor not found
for given call.*

Below is the Entry class, and a main method describing how I use it.
How can I fix this error to get the class compiling as part of x10.lang
package?

class Entry{
    private var name:String;
    private var parentEntryGR:GlobalRef[Entry];

    //constructor for the parent:only the parent has a name
    public def this(var name:String){
    this.name = name;
    }

    //constructor for the children, just pointing at the parent entry
    public def this(parentEntry:GlobalRef[Entry]){
        this.parentEntryGR = parentEntry;
    }

    public def printParentEntryName(){
    at(parentEntryGR)
    {
    Console.OUT.println(parentEntryGR().name);   /*Error: Method or static
constructor not found for given call.*/
    }
    }
    public def getParentEntryGR():GlobalRef[Entry] = parentEntryGR;
    public def setParentEntryGR(var parentGR:GlobalRef[Entry])
{this.parentEntryGR = parentGR;}

}


//Test class
public class TestGlobalRef {
    public static def main(val args:Rail[String]){
        //create the parent entry at place 0
        val parentEnt:Entry = new Entry("parent name");
        val parentEntGR = GlobalRef[Entry](parentEnt);
        parentEnt.setParentEntryGR(parentEntGR);

        for (p in Place.places())
        {
            at(p)
            {
                val entry:Entry;
                if (p.id != parentEntGR.home.id)
                    entry = new Entry(parentEntGR); //create children
Entries on other places
                else
                entry = at (parentEntGR) {parentEntGR()};

                entry.printParentEntryName();
            }
        }
    }
}

Thank you,
Sara

Re: [X10-core] Clocked finish implementation

[Olivier T. <ta...@us...>]

Sara,

The implicit call to Clock.make() is synthesized by the Lowering pass 
(Lowerer.java) of the x10 compiler in the override method (line 237).

Olivier

Sara Salem <sar...@gm...> wrote on 04/30/2014 09:51:31 PM:

> From: Sara Salem <sar...@gm...>
> To: x10...@li...
> Date: 04/30/2014 09:51 PM
> Subject: [X10-core] Clocked finish implementation
> 
> Hi All,
>   Where, in X10 source code, the implicit Clock object used by a 
> clocked finish is constructed?
> 
> Thank you.
> Sara
> 
------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
> unparalleled scalability from the best Selenium testing platform 
available.
> Simple to use. Nothing to install. Get started now for free."
> 
http://p.sf.net/sfu/SauceLabs_______________________________________________

> X10-core mailing list
> X10...@li...
> https://lists.sourceforge.net/lists/listinfo/x10-core

[X10-core] Clocked finish implementation

[Sara S. <sar...@gm...>]

Hi All,
  Where, in X10 source code, the implicit Clock object used by a clocked
finish is constructed?

Thank you.
Sara

Re: [X10-core] RFC: Integer literals

[Josh M. <jos...@an...>]

I realise that the case is closed and the jury has already rendered its 
verdict,  but is there a reason we can't use 'z' (= integer) rather than 
'n' (= natural number, non-negative integer) for a signed 32-bit int?

------------------------------------------
Josh Milthorpe

Postdoctoral Fellow, Research School of Computer Science
Australian National University, Building 108
Canberra, ACT 0200
Australia
Phone:  + 61 (0)2 61254478
Mobile: + 61 (0)407 940743
E-mail: jos...@an...
Web:    http://cs.anu.edu.au/~Josh.Milthorpe/

On 03/08/13 00:07, Jonathan Brezin wrote:
>
> Dave et al,
>
> As an application programmer mostly working in very weakly typed 
> languages like JavaScript, I was very sceptical when I first started 
> working in X10 -- how long ago?  5 or 6 years?  It took a while, but I 
> have become a real fan of being forced to say explicitly what each 
> identifier is, either in terms of the one value it will ever have, or 
> by writing out an honest, all i's dotted type expression.  This causes 
> me to be more sympathetic to the "no default" for literals than I 
> might otherwise be.
>
> Looking back to my early computing days--C and Bell Labs in the late 
> 1970's and early 80's--C's choice of being glib about what size things 
> were ("int" meant "the natural size integer for the machine in 
> question") led to no end of #ifdefs as machines made the leap from 16 
> to 32 bit integers, which led to code very easy to misread.  C's 
> semantics for numeric operators are still enormously complicated, as 
> anyone who has looked at the literature on random number generators 
> will agree, where that forest of #ifdefs rears its ugly head for the 
> sake only of machine independence.   Goodbye int, hello int32.
>
> So here we are again.  32 to 64 bits this time, but so what?  What was 
> "natural" is a year ago is no longer "natural" now.  The only 
> difference between our situation and C's is the relatively modest 
> amount of legacy code we are saddled with, and it's only literals that 
> need tweaking.  So bottom line:
>
> I think that "n" is better than "i" precisely because mathematicians 
> for two hundred years have used "i" differently, and "n" is a choice 
> that is mathematically in good taste (natural numbers).  I also think 
> (and few will agree with me) that numeric precision should always be 
> made explicit.  I am not even all that pleased with float versus 
> double:  how long until long doubles are the precision of choice for 
> HPC numeric problems, and are we going to go through this all over again?
>
> Jonathan
>
>
> Jonathan Brezin
> Research Staff Member
> IBM TJ Watson Research Labs
> 1101 KITCHAWAN RD
> ROUTE 134 / PO BOX 218
> YORKTOWN HEIGHTS NY 10598
>
> Phone: (914) 784-6728 (Tie: 863-6728)
>

Re: [X10-core] Fwd: Re: [X10-users] Performance tuning for the N Body problem

[Vijay S. <vi...@sa...>]

On 6/30/13 7:33 PM, Josh Milthorpe wrote:
> Hi all,
>
> I was planning to respond to Konstantina to suggest using an 
> accumulator variable.  However, I'm not sure of the current status of 
> accumulators.  Will the (undocumented) syntax from X10 v2.3 remain the 
> same for v2.4?  Will accumulators be documented in the language spec 
> as part of resolving XTENLANG-2789 ?
>
I dont believe Accumulators are fully implemented.

Konstantina should use collecting finish. That should work.

[X10-core] Fwd: Re: [X10-users] Performance tuning for the N Body problem

[Josh M. <jos...@an...>]

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

Re: [X10-core] general implementation of map/reduce

[David P G. <gr...@us...>]

Hi Josh,

	In general, I think the reason to have map/reduce/scan operations in
the library (as opposed to defined by the user in their application via the
normal iteration methods provided by the library) is to give efficient &
parallel implementations of the operations.

	In terms of semantics, I think that means the operations should be
defined to be may parallel (the implementation may implement some
operations in parallel, but may also implement some of them sequentially).
This gives the implementation the most flexibility to heuristically pick an
appropriate task-size to dynamically match the available resources.

	Doing a good job of dividing the work up into chunks and doing them
in parallel takes some amount of clever code, so it is appealing to do it
once and share it between multiple data structures.  However, the trick is
doing that in a way that the abstraction that enables a single map or
reduce implementation to work on multiple collection types doesn't
introduce so much overhead that the performance gained by clever coding of
the parallel work structure gets lost in the sequential overhead of object
allocation, indirection, and interface invocation.

	My intuition is that the general implementation would lose enough
performance that we'd end up with specialized ones for many of the data
structures, but I could be wrong.  It would be interesting to see how much
of a performance difference there is and understand how much of the gap is
fundamental and how much could be fixed via better optimization of the
sequential object-oriented X10 language features.

	For the specific case of Rail, we should bring back map/reduce
functions for Rail before we release 2.4.  Since Rail is a @NativeRep
class, we will probably do that by putting static functions into
x10.util.ArrayUtils (or similar) so that we can write them once in X10.

--dave