public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: dl256@columbia.edu To: gcc-gnats@gcc.gnu.org Subject: c++/7678: implicity typename deprecated inheritance problem Date: Wed, 21 Aug 2002 13:25:00 -0000 [thread overview] Message-ID: <20020821170059.5745.qmail@sources.redhat.com> (raw) >Number: 7678 >Category: c++ >Synopsis: implicity typename deprecated inheritance problem >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Aug 21 10:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: dl256@columbia.edu >Release: gcc-3.1 >Organization: >Environment: gnu-linux kernal 2.4.18 (i686) >Description: compile the attached file using: g++ -c experiment.cpp The compiler warns that "implicit typname is deprecated". . The base class is templated. It takes a traits structure as it's tmeplate argument, and then it creates typedefs in the public area of the class. The derived class is also templated, but it contains no typedefs. It is desirable to used the types defined in the base class in the derived class, without using the typename base<__traits>:: qualification. Is your interpretation of the specification correct for this case? This doesn't make sense to me. The new types should at lease be inherited in the derived class so that we can use them in the usual way (i.e., without full qualification using typename). >How-To-Repeat: Just compile the attached file and check the warnings. >Fix: Don't know. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="experiment.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="experiment.cpp" Ly8gQSB0ZXN0IGMrKyBjb2RlIHRvIGV4aGliaXQgYW4gdW5kZXNpcmVkIGZlYXR1cmUgb2YgaW4g Z2NjLTMuMQovLwovLyBUaGUgd2FybmluZyBpc3N1ZWQgYnkgdGhlIGNvbXBpbGVyIGhhcyB0byBk byB3aXRoCi8vICJpbXBsaWNpdCB0eXBlbmFtZSBkZXByZWNhdGVkIi4gIFdlIHdvdWxkIGxpa2Ug dG8gdXNlIHNpemVfdHlwZQovLyBhbmQgdmFsdWVfdHlwZSBpbiB0aGUgZGVyaXZlZCBjbGFzcyB3 aXRob3V0IHVzaW5nIHRoZSBsb25nCi8vIG5hbWVzIHN1Y2ggYXMgdHlwZW5hbWUgYmFzZTxfX3Ry YWl0cz46OnZhbHVlX3R5cGUuCgpzdHJ1Y3QgbXl0cmFpdHMgewogIHR5cGVkZWYgaW50ICAgIHNp emVfdHlwZTsKICB0eXBlZGVmIGRvdWJsZSB2YWx1ZV90eXBlOwp9OwoKdGVtcGxhdGUgPGNsYXNz IF9fdHJhaXRzPgpjbGFzcyBiYXNlIHsKcHVibGljOgogIHR5cGVkZWYgdHlwZW5hbWUgX190cmFp dHM6OnNpemVfdHlwZSAgICBzaXplX3R5cGU7CiAgdHlwZWRlZiB0eXBlbmFtZSBfX3RyYWl0czo6 dmFsdWVfdHlwZSAgIHZhbHVlX3R5cGU7CgogIGJhc2UodmFsdWVfdHlwZSB4XykgOiB4KHhfKSB7 fQoKcHJpdmF0ZToKICB2YWx1ZV90eXBlIHg7Cn07Cgp0ZW1wbGF0ZSA8Y2xhc3MgX190cmFpdHM+ CmNsYXNzIGFwcCA6IHB1YmxpYyBiYXNlPF9fdHJhaXRzPiB7CgpwdWJsaWM6CgogIC8vICoqKioK ICAvLyAqKioqIHdhcm5pbmdzIGlzc3VlZCBoZXJlCiAgLy8gKioqKgoKICBhcHAodmFsdWVfdHlw ZSB4XywgdmFsdWVfdHlwZSB5XykgOiBiYXNlPF9fdHJhaXRzPih4XyksIHkoeV8pIHt9Cgpwcml2 YXRlOgoKICAvLyAqKioqCiAgLy8gKioqKiBubyB3YXJuaW5ncyBoZXJlCiAgLy8gKioqKgogIHR5 cGVuYW1lIGJhc2U8X190cmFpdHM+Ojp2YWx1ZV90eXBlIHk7Cgp9OwoKaW50IG1haW4oKSB7CiAg YXBwPG15dHJhaXRzPiBvYmooMS4wLDIuMCk7CgogIHJldHVybiAwOwp9Cg==
next reply other threads:[~2002-08-21 17:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-21 13:25 dl256 [this message] 2002-08-21 17:16 nathan 2002-08-22 16:19 Gabriel Dos Reis
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=20020821170059.5745.qmail@sources.redhat.com \ --to=dl256@columbia.edu \ --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).