(j3.2006) About extending abstract types with deferred bindings

[Lionel, Steve]

Thanks, Malcolm - I understand now. I also see:

NOTE 7.52
Inaccessible components and bindings of the parent type are also inherited, but they remain inaccessible in
the extended type. Inaccessible entities occur if the type being extended is accessed via use association and
has a private entity.

Which resolves my confusion.

Steve

-----Original Message-----
From: j3-bounces at mailman.j3-fortran.org [mailto:j3-bounces at mailman.j3-fortran.org] On Behalf Of Cohen Malcolm
Sent: Thursday, September 08, 2016 2:05 AM
To: fortran standards email list for J3 <j3 at mailman.j3-fortran.org>
Subject: Re: (j3.2006) About extending abstract types with deferred bindings

<<<
Or maybe not. With the interp, the extended type clearly doesn?t inherit the private type-bound procedures, so the extension is ok? Still confused?
>>>

There is no doubt whatsoever:

"An extended type includes all of the type parameters, all of the 
components, and the nonoverridden (7.5.7.3) type-bound procedures of its 
parent type."

It's just that anything private is not accessible outside of the module.

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

_______________________________________________
J3 mailing list
J3 at mailman.j3-fortran.org
http://mailman.j3-fortran.org/mailman/listinfo/j3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6616 bytes
Desc: not available
Url : http://mailman.j3-fortran.org/pipermail/j3/attachments/20160908/c43b38f2/attachment-0001.bin