public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: fw@deneb.enyo.de To: gcc-gnats@gcc.gnu.org Subject: ada/4478: Scope of use_package_clause is wrong Date: Fri, 05 Oct 2001 05:26:00 -0000 [thread overview] Message-ID: <E15pUKA-0000uA-00@deneb.enyo.de> (raw) >Number: 4478 >Category: ada >Synopsis: Scope of use_package_clause is wrong >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: accepts-illegal >Submitter-Id: net >Arrival-Date: Fri Oct 05 05:26:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Florian Weimer >Release: 3.1 20011003 (experimental) >Organization: >Environment: System: Linux deneb 2.4.7 #3 Sat Jul 21 09:35:45 CEST 2001 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../configure --prefix=/opt/gcc-3 >Description: With GNAT, the scope of a use_package_clause in a context_clause incorrectly begins just after the use_package_clause, in contradiction to RM 8.4(6). As a consequence, GNAT compiles the illegal spec of package P3 below. (This problem was reported by Stephen Cole in <9pk4t7$tbm$1@trog.dera.gov.uk>.) >How-To-Repeat: Run the following code through gnatchop, and try to compile p3.ads. Compilation should fail, but it doesn't. --STX package P1 is pragma Pure; end; package P1.P2 is pragma Pure; end; with P1.P2; use P1; use P2; package P3 is pragma Pure; end; >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-10-05 5:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-05 5:26 fw [this message] 2003-05-12 8:36 Dara Hazeghi
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=E15pUKA-0000uA-00@deneb.enyo.de \ --to=fw@deneb.enyo.de \ --cc=gcc-gnats@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).