public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Tobias Burnus <tobias@codesourcery.com>, gcc-patches@gcc.gnu.org
Cc: gfortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH][pushed] fortran: remove 2 dead links [PR106636]
Date: Tue, 20 Sep 2022 14:24:39 +0200	[thread overview]
Message-ID: <2e27c67f-1a1f-d037-29ad-255a00e4f7c7@suse.cz> (raw)
In-Reply-To: <32a48c99-007a-5dc9-c78b-2134c6f3e2bc@codesourcery.com>

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

On 9/20/22 14:17, Tobias Burnus wrote:
> Hi Martin,
> 
> On 20.09.22 14:02, Martin Liška wrote:
>> diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi
>> @@ -455,9 +455,7 @@ version 2.6, @uref{https://www.openacc.org/}).  See
>>   The Fortran 95 standard specifies in Part 2 (ISO/IEC 1539-2:2000)
>>   varying length character strings.  While GNU Fortran currently does not
>>   support such strings directly, there exist two Fortran implementations
>> -for them, which work with GNU Fortran.  They can be found at
>> -@uref{https://www.fortran.com/@/iso_varying_string.f95} and at
>> -@uref{ftp://ftp.nag.co.uk/@/sc22wg5/@/ISO_VARYING_STRING/}.
>> +for them, which work with GNU Fortran.
> 
> Instead of removing the links, can we rather replace it by an updated link?
> 
> Richard Townsend has implemented the fortran.com version; webarchive
> show that was the 1.3-F version that is still available from his own
> homepage at:
> 
> http://user.astro.wisc.edu/~townsend/static.php?ref=iso-varying-string
> (BTW: I now also added Richard's website to web.archive.org.)
> 
> I don't think most users need this module, but still if it is mentioned,
> I does not harm to have the link available.

Thanks for the archeological work you did.
Sure, what about the suggested patch?

Martin

> 
> Tobias
> 
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

[-- Attachment #2: 0001-fortran-add-link-to-ISO_VARYING_STRING-module-PR1066.patch --]
[-- Type: text/x-patch, Size: 1194 bytes --]

From 64376d0f450b03e2bdaad486aaa5df8141b2dde1 Mon Sep 17 00:00:00 2001
From: Martin Liska <mliska@suse.cz>
Date: Tue, 20 Sep 2022 14:23:29 +0200
Subject: [PATCH] fortran: add link to ISO_VARYING_STRING module [PR106636]

	PR fortran/106636

gcc/fortran/ChangeLog:

	* gfortran.texi: Add back link to ISO_VARYING_STRING.
---
 gcc/fortran/gfortran.texi | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi
index 25410e6088d..4ab67700362 100644
--- a/gcc/fortran/gfortran.texi
+++ b/gcc/fortran/gfortran.texi
@@ -455,7 +455,8 @@ version 2.6, @uref{https://www.openacc.org/}).  See
 The Fortran 95 standard specifies in Part 2 (ISO/IEC 1539-2:2000)
 varying length character strings.  While GNU Fortran currently does not
 support such strings directly, there exist two Fortran implementations
-for them, which work with GNU Fortran.
+for them, which work with GNU Fortran. One can be found at
+@uref{http://user.astro.wisc.edu/~townsend/static.php?ref=iso-varying-string}.
 
 Deferred-length character strings of Fortran 2003 supports part of
 the features of @code{ISO_VARYING_STRING} and should be considered as
-- 
2.37.3


  reply	other threads:[~2022-09-20 12:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 12:02 Martin Liška
2022-09-20 12:17 ` Tobias Burnus
2022-09-20 12:24   ` Martin Liška [this message]
2022-09-20 13:38     ` Tobias Burnus

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=2e27c67f-1a1f-d037-29ad-255a00e4f7c7@suse.cz \
    --to=mliska@suse.cz \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tobias@codesourcery.com \
    /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).