[J3] Question about EVENT, LOCK and NOTIFY_TYPE as components
Malcolm Cohen
malcolm at nag-j.co.jp
Thu May 30 23:53:28 UTC 2024
It is covered by the more general constraint:
“C954 (R929) If SOURCE= appears, the declared type of source-expr shall not be EVENT_TYPE, LOCK_TYPE, or NOTIFY_TYPE from the intrinsic module ISO_FORTRAN_ENV, or have a potential subobject component that is a coarray or of type EVENT_TYPE, LOCK_TYPE, or NOTIFY_TYPE.”
Cheers,
--
..............Malcolm Cohen, NAG Oxford/Tokyo.
From: J3 <j3-bounces at mailman.j3-fortran.org> On Behalf Of Van Snyder via J3
Sent: Friday, May 31, 2024 2:56 AM
To: j3 at mailman.j3-fortran.org
Cc: Van Snyder <van.snyder at sbcglobal.net>
Subject: Re: [J3] Question about EVENT, LOCK and NOTIFY_TYPE as components
On Thu, 2024-05-30 at 14:25 +0000, Brad Richardson via J3 wrote:
An event variable shall not appear in a variable definition context
except as:
* the event-variable in an EVENT POST or EVENT WAIT statement
* an allocate-object
* an actual argument in a reference to a procedure with an explicit
interface if the corresponding dummy argument has INTENT (INOUT)
In the "allocate object" case, I assume SOURCE= should be excluded, but it appears not to be (maybe I missed it).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20240531/3059787a/attachment.htm>
More information about the J3
mailing list