A doubt about IMPORT and SELECT TYPE

A doubt about IMPORT and SELECT TYPE

[Jorge D'Elia]

Hi,

I have a doubt about IMPORT and SELECT TYPE, please see the 
forwarded message below (that also has a sample code), as well 

https://www.ibm.com/docs/en/xffbg/121.141?topic=attributes-import-fortran-2003

What is the correct way? Thanks.

Regards.
Jorge.

----- Forwarded message -----
From: "Intel Community" 
To: "Jorge D'Elia" <jdelia@cimec.unl.edu.ar>
Sent: Viernes, 2 de Junio 2023 10:28:31
Subject: Re: Bug with IMPORT and SELECT TYPE (Intel Community Subscription Update)

Hi jdelia,

OP1 (New Contributor II) posted a new reply in Intel® Fortran Compiler on 06-02-2023 10:28 AM in the Intel Community:

https://community.intel.com/t5/Intel-Fortran-Compiler/Bug-with-IMPORT-and-SELECT-TYPE/m-p/1492319/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExJRUxQQzhSUEVaS1RTfDE0OTIzMTl8U1VCU0NSSVBUSU9OU3xoSw#M166583

Subject:  Re: Bug with IMPORT and SELECT TYPE

Well, it appears that gfortran also gets it wrong... the use of an IMPORT statement is not limited to interfaces. 
See this paragraph from the Intel documentation: An IMPORT statement can appear in a submodule, module procedure, 
a contained procedure, the specification part of a BLOCK construct, or in an interface body. It can not appear in 
the specification part of a main program, external procedure, module, or block data except in an interface body.

--

Re: A doubt about IMPORT and SELECT TYPE

[Paul Richard Thomas]

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?

Thanks

Paul

On Fri, 2 Jun 2023 at 15:04, Jorge D'Elia via Fortran
<fortran@gcc.gnu.org> wrote:
>
> Hi,
>
> I have a doubt about IMPORT and SELECT TYPE, please see the
> forwarded message below (that also has a sample code), as well
>
> https://www.ibm.com/docs/en/xffbg/121.141?topic=attributes-import-fortran-2003
>
> What is the correct way? Thanks.
>
> Regards.
> Jorge.
>
> ----- Forwarded message -----
> From: "Intel Community"
> To: "Jorge D'Elia" <jdelia@cimec.unl.edu.ar>
> Sent: Viernes, 2 de Junio 2023 10:28:31
> Subject: Re: Bug with IMPORT and SELECT TYPE (Intel Community Subscription Update)
>
> Hi jdelia,
>
> OP1 (New Contributor II) posted a new reply in Intel® Fortran Compiler on 06-02-2023 10:28 AM in the Intel Community:
>
> https://community.intel.com/t5/Intel-Fortran-Compiler/Bug-with-IMPORT-and-SELECT-TYPE/m-p/1492319/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExJRUxQQzhSUEVaS1RTfDE0OTIzMTl8U1VCU0NSSVBUSU9OU3xoSw#M166583
>
> Subject:  Re: Bug with IMPORT and SELECT TYPE
>
> Well, it appears that gfortran also gets it wrong... the use of an IMPORT statement is not limited to interfaces.
> See this paragraph from the Intel documentation: An IMPORT statement can appear in a submodule, module procedure,
> a contained procedure, the specification part of a BLOCK construct, or in an interface body. It can not appear in
> the specification part of a main program, external procedure, module, or block data except in an interface body.
>
> --



-- 
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein

Re: A doubt about IMPORT and SELECT TYPE

[Paul Richard Thomas]

Hi Jorge,

PRs 108650/106035 cover this problem.

Thanks

Paul

On Fri, 2 Jun 2023 at 15:04, Jorge D'Elia via Fortran
<fortran@gcc.gnu.org> wrote:
>
> Hi,
>
> I have a doubt about IMPORT and SELECT TYPE, please see the
> forwarded message below (that also has a sample code), as well
>
> https://www.ibm.com/docs/en/xffbg/121.141?topic=attributes-import-fortran-2003
>
> What is the correct way? Thanks.
>
> Regards.
> Jorge.
>
> ----- Forwarded message -----
> From: "Intel Community"
> To: "Jorge D'Elia" <jdelia@cimec.unl.edu.ar>
> Sent: Viernes, 2 de Junio 2023 10:28:31
> Subject: Re: Bug with IMPORT and SELECT TYPE (Intel Community Subscription Update)
>
> Hi jdelia,
>
> OP1 (New Contributor II) posted a new reply in Intel® Fortran Compiler on 06-02-2023 10:28 AM in the Intel Community:
>
> https://community.intel.com/t5/Intel-Fortran-Compiler/Bug-with-IMPORT-and-SELECT-TYPE/m-p/1492319/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExJRUxQQzhSUEVaS1RTfDE0OTIzMTl8U1VCU0NSSVBUSU9OU3xoSw#M166583
>
> Subject:  Re: Bug with IMPORT and SELECT TYPE
>
> Well, it appears that gfortran also gets it wrong... the use of an IMPORT statement is not limited to interfaces.
> See this paragraph from the Intel documentation: An IMPORT statement can appear in a submodule, module procedure,
> a contained procedure, the specification part of a BLOCK construct, or in an interface body. It can not appear in
> the specification part of a main program, external procedure, module, or block data except in an interface body.
>
> --



-- 
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein

Re: A doubt about IMPORT and SELECT TYPE

[Steve Kargl]

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

Re: A doubt about IMPORT and SELECT TYPE

[Paul Richard Thomas]

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

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
>

Re: A doubt about IMPORT and SELECT TYPE

[Steve Kargl]

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