public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2732] fortran: remove 2 dead links [PR106636] Date: Tue, 20 Sep 2022 12:03:17 +0000 (GMT) [thread overview] Message-ID: <20220920120317.6B5F8385840F@sourceware.org> (raw) https://gcc.gnu.org/g:d99821624c340429b86855ffa99e731618b36c10 commit r13-2732-gd99821624c340429b86855ffa99e731618b36c10 Author: Martin Liska <mliska@suse.cz> Date: Tue Sep 20 14:02:34 2022 +0200 fortran: remove 2 dead links [PR106636] PR fortran/106636 gcc/fortran/ChangeLog: * gfortran.texi: Remove 2 dead links. Diff: --- gcc/fortran/gfortran.texi | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi index 59d673bfc03..25410e6088d 100644 --- 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. Deferred-length character strings of Fortran 2003 supports part of the features of @code{ISO_VARYING_STRING} and should be considered as
reply other threads:[~2022-09-20 12:03 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220920120317.6B5F8385840F@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).