public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "georggcc at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/55324] New: diagnostic about abstract new in type derivation misleading due to being overly terse Date: Wed, 14 Nov 2012 12:53:00 -0000 [thread overview] Message-ID: <bug-55324-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55324 Bug #: 55324 Summary: diagnostic about abstract new in type derivation misleading due to being overly terse Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: ada AssignedTo: unassigned@gcc.gnu.org ReportedBy: georggcc@googlemail.com When deriving an abstract type from a tagged type but omitting the record extension part, GNAT says that "abstract" is not allowed here. Actually it is, following LRM 3.4 about derived_type_definition (similarly, 12.5.1), but only if followed by the record extension part. Maybe the "here" of the message could be expanded a bit, "here[, only for ...]" package x is type T is abstract tagged null record; type S is abstract new T; -- with null record; end x; $ gnatmake -gnatwa -gnaty -gnatv x.ads gcc -c -gnatwa -gnaty -gnatv x.ads GNAT 4.8.0 20120611 (experimental) Copyright 1992-2012, Free Software Foundation, Inc. Compiling: x.ads (source file time stamp: 2012-11-14 12:13:28) 5. type S is abstract new T; -- with null record; | >>> "abstract" not allowed here, ignored 7 lines: 1 error gnatmake: "x.ads" compilation error
reply other threads:[~2012-11-14 12:53 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-55324-4@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).