(j3.2006) (SC22WG5.5646) [ukfortran] Another comment on Corrigendum 4

[Malcolm Cohen]

>Stopping at an unallocated allocatable is fine for C1290

No, it is not fine at all.  Whether an allocatable is unallocated is a 
runtime condition, it cannot be part of a constraint.

> Or is there a different objective for this constraint?

The objective is to prevent writing an incorrect program.  The whole purpose 
of all those purity constraints is to prevent writing a pure procedure that 
does not have side effects, and this is completely undermined if the pure 
procedure could have side effects depending on the value of an argument.

Cheers,
-- 
.......................Malcolm.