public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46321] [OOP] Polymorphic deallocation
Date: Mon, 07 May 2012 09:51:00 -0000	[thread overview]
Message-ID: <bug-46321-4-tOU98WmUo8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46321-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321

--- Comment #6 from janus at gcc dot gnu.org 2012-05-07 09:49:52 UTC ---
(In reply to comment #5)
> Looks to me like work on FINAL needs to be interfaced here anyway. Naive view
> is that $free points to a FINAL if there is one, or to a default when there's
> no FINAL, but the hookup work is the same..

Yes, in principle I would agree with this view. Therefore implementing 'plain'
polymorphic deallocation would be the logical fist step to FINAL.


  parent reply	other threads:[~2012-05-07  9:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 18:37 [Bug fortran/46321] New: " janus at gcc dot gnu.org
2010-11-05 21:02 ` [Bug fortran/46321] " burnus at gcc dot gnu.org
2011-02-09 14:03 ` burnus at gcc dot gnu.org
2011-02-21 15:11 ` janus at gcc dot gnu.org
2011-11-26 14:33 ` burnus at gcc dot gnu.org
2012-01-29 14:37 ` burnus at gcc dot gnu.org
2012-05-07  9:34 ` sfilippone at uniroma2 dot it
2012-05-07  9:51 ` janus at gcc dot gnu.org [this message]
2013-07-22  7:31 ` janus at gcc dot gnu.org
2013-08-08 14:36 ` janus at gcc dot gnu.org

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=bug-46321-4-tOU98WmUo8@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).