https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106035
--- Comment #6 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Fri, Jun 02, 2023 at 05:51:17PM +0000, jde...@santafe-conicet.gov.ar wrote: > > --- Comment #5 from Jorge D'Elia <jde...@santafe-conicet.gov.ar> --- > > The access restriction is a reason of the use IMPORT statements in the > projects, since it is a very convenient and nifty way to detect any name > collision between local entities and host-associated entities, and well as, in > BLOCK statements, for the same purpose. Jorge, I agree with you 100% on the usefulness of IMPORT. The 2nd patch I attached to this PR is almost complete. That is, 'import', 'import, none', and 'import, all' work as defined in F2018. Unfortunately, 'import, only :: a, b, etc' does not work and I haven't had time to work out the details. My first thought is to create a list of allowed use-associated symbols. The list would be added to the current namespace after verifying the symbols are in a parent namespace, but that's as far as I've gotten.
