From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Fri Jan 22 00:52:44 2016
Return-Path: <owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id 0AA15358651; Fri, 22 Jan 2016 00:52:43 +0100 (CET)
Delivered-To: sc22wg5@open-std.org
Received: from nag-j.co.jp (bvdeuz19.secure.ne.jp [180.222.80.19])
	by www.open-std.org (Postfix) with SMTP id C7B7E3566C1
	for <sc22wg5@open-std.org>; Fri, 22 Jan 2016 00:52:35 +0100 (CET)
Received: (qmail 71764 invoked from network); 22 Jan 2016 08:52:32 +0900
Received: from unknown (HELO Maru10) (218.42.159.105)
  by 0 with SMTP; 22 Jan 2016 08:52:32 +0900
Message-ID: <3DB49A96D786481E95DE0FDD1177C4DD@Maru10>
From: "Cohen Malcolm" <malcolm@nag-j.co.jp>
To: "sc22wg5" <sc22wg5@open-std.org>
References: <20160121211113.AE41F35725F@www.open-std.org>
In-Reply-To: <20160121211113.AE41F35725F@www.open-std.org>
Subject: Re: [ukfortran] (SC22WG5.5641) Is LOCK_TYPE still not locked up?
Date: Fri, 22 Jan 2016 08:53:19 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

<<<
type :: T1
end type T1

type, extends(t1) :: T2
  type(lock_type) :: L
end type T2
>>>

This is already invalid.

C438 (R426) If EXTENDS appears and the type being defined has a potential 
subobject component of type EVENT_TYPE or LOCK_TYPE from the intrinsic 
module ISO_FORTRAN_ENV, its parent type shall be EVENT_TYPE or LOCK_TYPE or 
have a potential subobject component of type EVENT_TYPE or LOCK_TYPE.

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