John, Replying to the remaining parts of your message...
> In privatization, why are the dsiGetPrivatizeData() methods needed? > Since dsiPrivatize(privatizeData) has access to "this", why can't it > just get values from that? Yes you can if you prefer. The intention of dsiGetPrivatizeData() and privatizeData is that 'privatizeData' can be transferred to another locale all in one shot (a single message across the network). By contrast, if you say, e.g., this.targetLocDom.dims(), this will involve one or more additional messages. > Also, is there a way to explicitly request a reprivatization? Yes, invoke: _reprivatize(A._value) Note that at present this is "getting under the hood", not an official part of Chapel. > I have c/c++ background where it has to be explicitly stated whether > something is to be stored as pointer or in place, so I sometimes find > it rather confusing that some types are implicitly > stored/passed/copied/assigned as references while others are not... In my mind, records are like structs in C and classes are like struct pointers. Out of curiousity, which fields are challenging to keep track of? Vassily ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
