public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "charlet at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/16086] Legal program rejected, procedure of protected object should be visible
Date: Thu, 03 May 2007 08:25:00 -0000	[thread overview]
Message-ID: <20070503082530.12495.qmail@sourceware.org> (raw)
In-Reply-To: <bug-16086-286@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from charlet at gcc dot gnu dot org  2007-05-03 09:25 -------
The error message looks valid to me: it's not a matter of visibility: the
protected procedure is visible, but does not match, since it's not a
procedure, it's a protected procedure.

Arno


-- 

charlet at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


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


       reply	other threads:[~2007-05-03  8:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16086-286@http.gcc.gnu.org/bugzilla/>
2007-05-03  8:25 ` charlet at gcc dot gnu dot org [this message]
2007-05-03 18:27 ` ludovic at ludovic-brenta dot org
2008-04-12  1:32 ` sam at gcc dot gnu dot org
2008-04-15 11:04 ` sam at gcc dot gnu dot org
2008-04-15 11:05 ` sam at gcc dot gnu dot org
2004-06-19 15:04 [Bug ada/16086] New: " ludovic dot brenta at insalien dot org
2004-06-19 16:42 ` [Bug ada/16086] " pinskia at gcc dot gnu dot org
2004-10-29 14:36 ` pinskia at gcc dot gnu dot org
2004-10-29 14:36 ` pinskia at gcc dot gnu dot org
2004-10-29 14:47 ` pinskia at gcc dot gnu dot org
2004-11-01  1:49 ` pinskia at gcc dot gnu dot 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=20070503082530.12495.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: 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).