public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sam at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/23390] abstract function in private part not overloading previous function is not allowed Date: Mon, 17 Nov 2008 20:17:00 -0000 [thread overview] Message-ID: <20081117201556.26718.qmail@sourceware.org> (raw) In-Reply-To: <bug-23390-10930@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from sam at gcc dot gnu dot org 2008-11-17 20:15 ------- This is fixed in GCC 4.4.0 and gives the expected error. GNAT 4.4.0 20081116 (experimental) Copyright 1992-2008, Free Software Foundation, Inc. Compiling: three.adb (source file time stamp: 2008-11-17 20:14:51) ==============Error messages for source file: one.ads 11. function Func (X : in Type_T) return Type_T is abstract; | >>> abstract subprograms must be visible (RM 3.9.3(10)) -- sam at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23390
parent reply other threads:[~2008-11-17 20:17 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <bug-23390-10930@http.gcc.gnu.org/bugzilla/>]
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=20081117201556.26718.qmail@sourceware.org \ --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: 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).