From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Thu Aug 4 11:38:52 2022 Return-Path: X-Original-To: sc22wg5-dom9 Delivered-To: sc22wg5-dom9@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 8363E358D4B; Thu, 4 Aug 2022 11:38:52 +0200 (CEST) Delivered-To: sc22wg5@open-std.org Received: from nag-j.co.jp (bvdeuz19.secure.ne.jp [180.222.80.19]) by www.open-std.org (Postfix) with SMTP id 6DD45358C4E for ; Thu, 4 Aug 2022 11:38:50 +0200 (CEST) Received: (qmail 95189 invoked from network); 4 Aug 2022 18:38:48 +0900 Received: from unknown (HELO Maru10) (218.42.159.105) by 0 with SMTP; 4 Aug 2022 18:38:48 +0900 From: "Malcolm Cohen" To: "'Mikael Morin'" , Cc: "'Harald Anlauf'" References: <20220802175930.8F3FD358D05@www.open-std.org> <20220804024959.CBCF1358D31@www.open-std.org> <5dbda2fc-d082-2845-81a0-5e004437b338@orange.fr> In-Reply-To: <5dbda2fc-d082-2845-81a0-5e004437b338@orange.fr> Subject: RE: [SC22WG5.6416] RE: [ukfortran] Request for interpretation of compile-time restrictions on ASSOCIATED Date: Thu, 4 Aug 2022 18:38:48 +0900 Message-ID: <017d01d8a7e5$ffa23700$fee6a500$@nag-j.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHI9uPM5vLHaBN0NQ6f8hinURbdBQGV+BhWAiIOpjitoBxq8A== Content-Language: ja Sender: owner-sc22wg5@open-std.org Precedence: bulk >>, ASSOCIATED will return .FALSE.=20 >> because the shapes are not the same. ASSOCIATED is a much stronger=20 >> test than mere address comparison. >> >I see. In other words, ASSOCIATED doesn=E2=80=99t mean exactly the = same as "POINTER and TARGET have been pointer-associated before". The = semantics differs when bounds remapping is involved. Actually, there are other situations where the shape may differ, e.g. = when argument association or storage association is involved - this is = since Fortran 90. It is not only bounds remapping. Cheers, --=20 ..............Malcolm Cohen, NAG Oxford/Tokyo.