Hi,

I just stumbled upon this problem:

MODULE m1

TYPE t1
CONTAINS
PROCEDURE, NOPASS, PRIVATE :: proc
END TYPE t1

CONTAINS

SUBROUTINE proc ()
END SUBROUTINE proc

END MODULE m1

MODULE m2

TYPE, EXTENDS(t1) :: t2
CONTAINS
GENERIC :: gen => proc
END TYPE t2

END MODULE m2

Daniel Kraft wrote:

USE m1 here of course, sorry for the mistake.

Daniel Kraft wrote:

No, that would not be a reason for it to be invalid.

Private things can be made accessible in many ways. It is a fundamental
error to think that the private atribute on something means that the
entity cannot be accessed outside of the module.

The *ONLY* thing that the private attribute does is prevent the export
of the particular identifier (usually a name). It does *NOT* prevent
access to the inderlying entity by any other means that might happen to
not require using the identifier in question outside of the module.

For a trivial example, one could have an entity whose name is declared
private, but which is also the target of a public pointer. There are
other ways as well.

Another way of expressing this is that the private attribute attaches
only to the identifier(name), rather than to the underlying entity.

Richard Maine wrote:

Thanks Richard, your explanation was exactly what I was looking for! I
already supposed that the code was valid but wanted to get some opinions
on it (as I wouldn't really claim I know F2003 well).

Yours,
Daniel