public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8176: C++ const**, doesn't implictly cast
Date: Wed, 09 Oct 2002 12:46:00 -0000	[thread overview]
Message-ID: <20021009194602.27126.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

The following reply was made to PR c++/8176; it has been noted by GNATS.

From: Andreas Schwab <schwab@suse.de>
To: charles@kde.org
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/8176: C++ const**, doesn't implictly cast
Date: Wed, 09 Oct 2002 21:42:03 +0200

 charles@kde.org writes:
 
 |> class Bleh { };
 |> 
 |> void foo(const Bleh **) { }
 |> int main(int, char **)
 |> {
 |> 	Bleh *bleh;
 |> 	foo(&bleh); // broken
 |> 
 |> 	Bleh **bar;
 |> 	foo(bar); // broken
 |> 
 |> 	foo(const_cast<const Bleh**>(bar)); // works
 |> 
 |> 	const Bleh **works;
 |> 	foo(works); // works
 |> }
 |> 
 |> This should work, as <Bleh**> can be casted to <const Bleh**> implicitly
 
 No, you can't.
 
 class Bleh { int what; };
 const Bleh const_bleh;
 void foo(const Bleh **bleh)
 {
    *bleh = &const_bleh;
 }
 int main()
 {
   Bleh *bleh;
   foo(&bleh);        // assume this is valid
   (*bleh)->what = 1; // modifying const_bleh!
 }
 
 Andreas.
 
 -- 
 Andreas Schwab, SuSE Labs, schwab@suse.de
 SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
 Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
 "And now for something completely different."


             reply	other threads:[~2002-10-09 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 12:46 Andreas Schwab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-09 13:31 nathan
2002-10-09 13:06 Charles Samuels
2002-10-09 12:06 charles

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=20021009194602.27126.qmail@sources.redhat.com \
    --to=schwab@suse.de \
    --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: link
Be 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).