USE statement – wish: permit specifying additionally the access-spec

[certik]

Tobias Burnus wrote:

I want to suggest to permit the 'access-spec' to the use-stmt to set the
public/private default for the symbols use-associated (overridable by an
explicit access-stmt). – Thoughs?

Real-world use case the following:

I have two modules, one contains some definitions of parameters and the
other contains some internal procedures. I now use-associate the two and
what I would like to do is the following.

Note the 'use, private' and 'use, public' with the access-spec.
Currently, I end up using 'private' and then adding 'public' for all
symbols from 'openacc_kinds', which is neither very readable nor
maintainable.

module openacc
   use, private :: openacc_internal
   use, public :: openacc_kinds
   implicit none (type, external)

   private
   public :: acc_get_num_devices

   interface acc_get_device_type
      ! shall be private, from openacc_internal
     procedure :: acc_get_device_type_h
   end interface

[certik]

Bill Long wrote:

We already allow

module A
   use B
   private :: B

which has the effect of making everything accessed from B private. Hence the things public in B do not “leak” through to a scope that as a USE A.

Tobias replied:

I had missed this addition of Fortran 2018; Fortran 2008 didn't allow it.*

I still believe that a use-stmt with access-spec is more readable than
use-stmt + access-stmt, but I agree that the functionality is already
covered. Hence, I think one should still (re)consider it – but with low
priority.

[aradi]

I also think, that the use-stmt with access spec would be much more readable. Especially, with the original syntax, can you tell without detailed knowledge of the standard, what the public :: statement would make private? (Or is the code not-standard conforming at all?)

module B
end module B

module C
  integer, parameter :: B = 1
end module C

module A
  use B
  use C
  private :: B
end module A

Writing on the other hand

module A
  use, private :: B
  use, public :: C

would be obvious, I guess.

[qolin1]

Yes, USE, PUBLIC and USE, PRIVATE is on my wish-list too.