Re: A doubt about IMPORT and SELECT TYPE

[Steve Kargl <sgk@troutmask.apl.washington.edu>]

Oh, I'm not asking you or any of the other regular contributors
to gfortran to pick up my WIP patch and finish the last 5%.  Now,
lurkers on the mailing list, who have always wanted to give back,
well I'm more than willing to help explain the patch and what I
think needs to be done if they are so inclined to get their hands
dirty.

IMPORT is an interesting construct.  Originally, all entities 
are blocked from host assocation into an INTERFACE, so J3 
invented IMPORT to allow one to cherry pick entities from the
host.  gfortran's implementation is fairly straightforward.
In F2018, J3 extended IMPORT to block host-association in for
example a contained subprogram or BLOCK construct.  This seems
like a logical and good thing; except this is the complete
opposite of its original use.  Undoing/revising gfortran'sr
original implemenation of IMPORT is a bit more challenging.

-- 
steve

On Fri, Jun 02, 2023 at 09:14:01PM +0100, Paul Richard Thomas wrote:
> Hi Steve,
> 
> As noted in the previous email :-), although I didn't mention the partially
> cooked patch.
> 
> One day, once F2003 is sorted, I might turn to F2008/18!
> 
> Cheers
> 
> Paul
> 
> 
> On Fri, 2 Jun 2023, 16:27 Steve Kargl via Fortran, <fortran@gcc.gnu.org>
> wrote:
> 
> > On Fri, Jun 02, 2023 at 03:53:44PM +0100, Paul Richard Thomas via Fortran
> > wrote:
> > > Hi Jorge,
> > >
> > > As I posted in the Intel Community, the error generated by gfortran
> > > (and nagfor) is consistent with the F2003 constraint: C1210 (R1209)
> > > The IMPORT statement is allowed only in an interface-body.
> > >
> > > Could you please raise a problem report in gcc Bugzilla?
> > >
> >
> > There already is a PR about IMPORT.  See
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106035
> >
> > There is a patch that is 95-ish% complete.  The last
> > 5% is the hard part, which it seems no one has had
> > time or ideas on how to finish the patch.
> >
> > --
> > Steve
> >

-- 
Steve