public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8500: Allows cast to private base class Date: Mon, 11 Nov 2002 04:16:00 -0000 [thread overview] Message-ID: <20021111121604.6826.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8500; it has been noted by GNATS. From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/8500: Allows cast to private base class Date: 11 Nov 2002 12:36:48 +0100 Wolfgang Bangerth <bangerth@ticam.utexas.edu> writes: | The following reply was made to PR c++/8500; it has been noted by GNATS. | | From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> | To: "Harald H. Soleng" <Harald.Soleng@nr.no> | Cc: gcc-gnats@gcc.gnu.org | Subject: Re: c++/8500: Allows cast to private base class | Date: Fri, 8 Nov 2002 14:03:20 -0600 (CST) | | > You should not get an error with old style c-casting. | > However, with | > | > Base* b1 = static_cast<Base*> d1; | > | > on the second line of main you should. Here is the error message from | > the native Sun CC compiler: | > "Error: Using static_cast to convert from Derived* to Base* not allowed." | | Uhm, I don't think you can work around access control rules just by using | a C-style cast over a static_cast, can you? old-style casts don't chech acess control. New-style casts do, however. -- Gaby
next reply other threads:[~2002-11-11 12:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-11 4:16 Gabriel Dos Reis [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-08 12:06 Wolfgang Bangerth 2002-11-08 7:02 bangerth 2002-11-08 6:58 bangerth
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=20021111121604.6826.qmail@sources.redhat.com \ --to=gdr@integrable-solutions.net \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).