(j3.2006) STAT= and integer kind

[Malcolm Cohen]

Oops, I got this confused with the other paper on relaxing default integer 
constraints... my apologies.

>in the current TS18508 draft from May,

That would be the about-to-be-superceded draft...

> the collectives take for the STAT
>argument a default-kind integer. On the other hand, 14-173r2 suggest to
>add a STAT= to the atomic intrinsics which can be any integer kind.
>
>I think it makes sense to be consistent.

In principle I agree.

And you are right, 173r2 is applying changes to the TS (and indirectly to F2015 
via F2008).  Lots of opportunities for confusion there.  Bill Long will be 
producing a new draft of the TS shortly.

>Hmm, but F2008 also supports nondefault-kind integers for STAT=, see,
>e.g., "R628 stat-variable is scalar-int-variable". Admittedly, many
>(all?) of the STATUS= arguments of the intrinsics use a default-kind
>integer.

The latter is being improved.  OTOH, having no restrictions on the kind of 
integer is not necessarily a good idea, since oftimes the value being assigned 
is going to be out of range if you only supply an 8-bit integer (especially if 
the compiler has a unified set of error status codes).  It is better (for 
portability) if the standard makes some minimal requirements...

Cheers,
-- 
................................Malcolm Cohen, Nihon NAG, Tokyo.