public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janus Weil <janus@gcc.gnu.org>
To: Tobias Burnus <burnus@net-b.de>
Cc: gfortran <fortran@gcc.gnu.org>, gcc patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] Update Fortran entry at gcc-4.5/changes.html
Date: Tue, 01 Dec 2009 23:29:00 -0000	[thread overview]
Message-ID: <854832d40912011430y76e4b669r86fb470d75261aa@mail.gmail.com> (raw)
In-Reply-To: <4B151475.6080305@net-b.de>

> Index: changes.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.5/changes.html,v
> retrieving revision 1.52
> diff -u -r1.52 changes.html
> --- changes.html        29 Nov 2009 10:46:18 -0000      1.52
> +++ changes.html        1 Dec 2009 13:01:01 -0000
> @@ -355,11 +355,11 @@
>        pointer with <code>PASS</code> attribute now have to use
>        <code>CLASS</code> in line with the Fortran 2003 standard; the
>        workaround to use <code>TYPE</code> is no longer supported.</li>
> -       <li>Experimental, incomplete support for polymorphism, including
> -       <code>CLASS</code> (as allocatable or dummy), <code>SELECT
> TYPE</code>
> -       and dynamic dispatch of type-bound procedure calls. Some features do
> -       not work yet such as unlimited polymorphism (<code>CODE(*)</code>),
> -       <code>CLASS IS</code>, <code>EXTENDS_TYPE_OF</code>.</li>
> +       <li><a href="http://gcc.gnu.org/wiki/OOP">Experimental, incomplete
> +       support for polymorphism</a>, including <code>CLASS</code> (as
> +       allocatable or dummy), <code>SELECT TYPE</code> and dynamic dispatch

Just a detail: If one mentions 'allocatable' and 'dummy' here, one
should also mention 'pointer' (or just leave all three out, since each
CLASS variable has to be one of those anyway).

Cheers,
Janus

      parent reply	other threads:[~2009-12-01 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 13:05 Tobias Burnus
2009-12-01 14:00 ` Steven Bosscher
2009-12-02 13:17   ` Tobias Burnus
2009-12-01 23:29 ` Janus Weil [this message]

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=854832d40912011430y76e4b669r86fb470d75261aa@mail.gmail.com \
    --to=janus@gcc.gnu.org \
    --cc=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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: 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).