From: Jorge D'Elia <jdelia@intec.unl.edu.ar>
To: Gfortran List <fortran@gcc.gnu.org>
Subject: A doubt about IMPORT and SELECT TYPE
Date: Fri, 2 Jun 2023 11:12:14 -0300 (ART) [thread overview]
Message-ID: <1260414420.3647.1685715134551.JavaMail.zimbra@intec.unl.edu.ar> (raw)
In-Reply-To: <6b48bc0f-043f-4635-abaf-bac09d67323b.1685712510891@community.intel.com>
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.
--
next parent reply other threads:[~2023-06-02 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6b48bc0f-043f-4635-abaf-bac09d67323b.1685712510891@community.intel.com>
2023-06-02 14:12 ` Jorge D'Elia [this message]
2023-06-02 14:53 ` Paul Richard Thomas
2023-06-02 15:22 ` Steve Kargl
2023-06-02 20:14 ` Paul Richard Thomas
2023-06-02 21:04 ` Steve Kargl
2023-06-02 15:19 ` Paul Richard Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1260414420.3647.1685715134551.JavaMail.zimbra@intec.unl.edu.ar \
--to=jdelia@intec.unl.edu.ar \
--cc=fortran@gcc.gnu.org \
--cc=jdelia@cimec.unl.edu.ar \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).