public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "simon at pushface dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/24167] New: Visibility of private component of parent in child generic, generic compiles but instantiation doesn't Date: Sun, 02 Oct 2005 17:09:00 -0000 [thread overview] Message-ID: <bug-24167-303@http.gcc.gnu.org/bugzilla/> (raw) The example (which I will upload directly) fails as follows: grendel:~/tmp/visibility simon$ gnatmake -c -u -f actual-s.ads gcc -c actual-s.ads actual-s.ads:4:01: instantiation error at basis-second.adb:4 actual-s.ads:4:01: no selector "Started" for type "Base" defined at basis-second.ads:4, instance at line 4 gnatmake: "actual-s.ads" compilation error I think the code should have compiled, because the selector Started is defined in the private part of the parent package Basis. However grendel:~/tmp/visibility simon$ gnatmake -c -u -f basis-second.adb gcc -c basis-second.adb grendel:~/tmp/visibility simon$ In other words, the generic compiles but the instantiation doesn't, which is not meant to happen. -- Summary: Visibility of private component of parent in child generic, generic compiles but instantiation doesn't Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: ada AssignedTo: unassigned@gcc.gnu.org ReportedBy: simon@pushface.org GCC build triplet: powerpc-apple-darwin7.9.0 GCC host triplet: powerpc-apple-darwin7.9.0 GCC target triplet: powerpc-apple-darwin7.9.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24167
next reply other threads:[~2005-10-02 17:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-02 17:09 simon at pushface dot org [this message] 2005-10-02 17:11 ` [Bug ada/24167] " simon at pushface dot org 2005-10-02 17:52 ` laurent at guerby dot net 2009-01-02 15:20 ` laurent at guerby dot net 2010-01-07 17:34 ` simon at pushface 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=bug-24167-303@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: 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).