(j3.2006) (SC22WG5.5425) WG5 straw ballot on N2040

[Bill Long]

Definitely worth considering.  Thanks, Reinhold.

Cheers,
Bill

On Jan 19, 2015, at 10:59 AM, Bader, Reinhold <Reinhold.Bader at lrz.de> wrote:

> Alternatively, one could consider making the notation analogous to the
> TEAM_ID one, say
> 
> type(team_type) :: ancestor
> 
> a[i, TEAM=ancestor] = ...
> 
> Some characters more to type in, but also more consistent.
> 
> Cheers 
> Reinhold
> 
> 
>> -----Urspr?ngliche Nachricht-----
>> Von: j3-bounces at mailman.j3-fortran.org [mailto:j3-bounces at mailman.j3-
>> fortran.org] Im Auftrag von Bill Long
>> Gesendet: Montag, 19. Januar 2015 15:02
>> An: fortran standards email list for J3
>> Betreff: Re: (j3.2006) (SC22WG5.5425) WG5 straw ballot on N2040
>> 
>> 
>> On Jan 18, 2015, at 7:59 PM, Malcolm Cohen <malcolm at nag-j.co.jp> wrote:
>> 
>>> 
>>> (c) I do not agree with the syntax for specifying a team variable in
>>> an image-selector, as we use double colons following type-specs and
>>> other related attributes, which this is certainly not.  A single colon would be
>> acceptable.
>> 
>> 
>> We did consider both single and double colon notation.  The problem with the
>> single colon notation is that it visually looks like the notation for an array
>> section. While we currently don't allow co-sections, it is a fairly obvious
>> extension in the future. Earlier coarray extensions had already allowed it.   Even
>> though the compiler would have no problem figuring out the meaning in the
>> single colon case , since the variable is a team variable, that is not obvious
>> visually when reading the statement.   Arguably, someone could perversely
>> name a team variable INTEGER and also produce an awkward looking
>> designator with the double colon notation.  But that seemed the lesser of the
>> two possible evils.
>> 
>> Cheers,
>> Bill
>> 
>> 
>> Bill Long                                                                       longb at cray.com
>> Fortran Technical Suport  &                                  voice:  651-605-9024
>> Bioinformatics Software Development                     fax:  651-605-9142
>> Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101
>> 
>> 
>> _______________________________________________
>> J3 mailing list
>> J3 at mailman.j3-fortran.org
>> http://mailman.j3-fortran.org/mailman/listinfo/j3
> _______________________________________________
> J3 mailing list
> J3 at mailman.j3-fortran.org
> http://mailman.j3-fortran.org/mailman/listinfo/j3

Bill Long                                                                       longb at cray.com
Fortran Technical Suport  &                                  voice:  651-605-9024
Bioinformatics Software Development                     fax:  651-605-9142
Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101