(j3.2006) C12101 and C12102

[Rafik Zurob]

Thanks, John (and Van).  I usually use newer revisions, but only had the 
2010 one handy yesterday.  In any case, it's a good thing this was raised. 
 We released support for ERROR STOP in 2012 so our implementation used the 
old rule.  That's fixed now.

Regards

Rafik

j3-bounces at mailman.j3-fortran.org wrote on 31/05/2014 09:15:47 AM:

> From: John Reid <John.Reid at stfc.ac.uk>
> To: fortran standards email list for J3 <j3 at mailman.j3-fortran.org>, 
> Date: 31/05/2014 09:16 AM
> Subject: Re: (j3.2006) C12101 and C12102
> Sent by: j3-bounces at mailman.j3-fortran.org
> 
> 
> 
> Rafik Zurob wrote:
> >> As for ERROR STOP in pure, it's not allowed.  In F2008 (7th June 2010
> >> draft):
> >> C1287 A pure subprogram shall not contain a stop-stmt or
> > error-stop-stmt.
> >
> > Sigh.  I knew something was bound to go wrong when I consulted the
> > 4-year-old draft.  The newer drafts don't have "or error-stop-stmt".
> 
> This is a difference between F2008 and its revision. WG5 decided last 
> year to adopt this proposal (see N1975):
> 
> Number: UK-06
> Title: Remove restriction on ERROR STOP
> Status: For Consideration
> Basic Functionality:
> Remove restriction on error-stop
> Rationale:
> There is no standard way to issue a diagnostic message from a PURE
> procedure.  A program should be able to execute an error termination
> with a meaningful message.
> 
> Specification:
> Remove the restriction on the appearance of an ERROR STOP statement
> in a PURE procedure.
> 
> Syntax:
> Delete 'or <<error-stop-stmt>>" in C1287 [313:8].
> 
> Cheers,
> 
> John.
> _______________________________________________
> J3 mailing list
> J3 at mailman.j3-fortran.org
> http://mailman.j3-fortran.org/mailman/listinfo/j3
>