public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92472] enhancement: 5 * constify some parameters
Date: Wed, 06 May 2020 10:55:11 +0000	[thread overview]
Message-ID: <bug-92472-4-HHvcrTdAbU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92472-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92472

--- Comment #7 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Jonathan Wakely from comment #6)
> This is 400% wrong. It doesn't even address what cppcheck is complaining
> about, and cppcheck is drunk anyway. 

Thanks for your explanation. 
I am a bit confused by it, so further explanation sought, please. 

> Those parameter can NOT be const, because *__b1 and *__b2 will not 
> compile if they're const, because operator* is not const.

My understanding of C++, frayed somewhat since 1988, is that operator * 
being const is a different language feature to parameters being const.

Unless you know different.

> But what about testing them?

Any guidance on fixing this problem, if it is a problem at all,
would be most welcome.

  parent reply	other threads:[~2020-05-06 10:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92472-4@http.gcc.gnu.org/bugzilla/>
2020-05-05 13:59 ` cvs-commit at gcc dot gnu.org
2020-05-05 14:00 ` cvs-commit at gcc dot gnu.org
2020-05-05 14:01 ` marxin at gcc dot gnu.org
2020-05-06 10:07 ` redi at gcc dot gnu.org
2020-05-06 10:55 ` dcb314 at hotmail dot com [this message]
2020-05-06 14:00 ` redi at gcc dot gnu.org
2020-05-06 14:08 ` redi at gcc dot gnu.org
2020-05-06 15:08 ` dcb314 at hotmail dot com
2020-05-06 15:23 ` redi at gcc dot gnu.org
2020-05-06 15:30 ` redi at gcc dot gnu.org
2020-05-07 20:43 ` cvs-commit at gcc dot gnu.org

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-92472-4-HHvcrTdAbU@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: 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).