(j3.2006) Select Rank

Bill Long longb
Tue Feb 17 18:27:37 EST 2015

On Feb 17, 2015, at 5:06 PM, Robert Corbett <robert.corbett at oracle.com> wrote:

> On 02/17/15 14:38, Bill Long wrote:
>> The A is a variable that is an array.  How many places in the standard do we assume that the number of subscripts in an array element designator is the same as the declared rank of the array?  Do we really think that the edits to implement this feature would address all of those places?   Not to mention internal compiler variable descriptions that incorporate this assumption that would face being changed.  [I?m not sure what you mean by ?construct name?.  We have a syntax term<construct-name>, but it has nothing to do with this example. Construct names do not have ranks.]
> I was sloppy.  By a construct name, I meant a construct entity that is a name.  Something like an associate name, which is similar to the case here.  Associate names can have rank.

Ah, right.  Van referred to SELECT TYPE, not SELECT CASE.  An associate name is less disruptive, since it is not declared.  Whether we want to propose this for F2020 is another question.  Does it really solve an existing problem?


> Bob Corbett
> _______________________________________________
> 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

More information about the J3 mailing list