From: Tobias Burnus <tobias@codesourcery.com>
To: "Martin Liška" <mliska@suse.cz>, 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:17:08 +0200 [thread overview]
Message-ID: <32a48c99-007a-5dc9-c78b-2134c6f3e2bc@codesourcery.com> (raw)
In-Reply-To: <bd2cf6a7-8775-3b9c-2fc5-910ebef180f4@suse.cz>
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.
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
next prev parent reply other threads:[~2022-09-20 12:17 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 [this message]
2022-09-20 12:24 ` Martin Liška
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=32a48c99-007a-5dc9-c78b-2134c6f3e2bc@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).