public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: send2pradeep@yahoo.com To: gcc-gnats@gcc.gnu.org Subject: c/7273: having problem with pointer to pointer with const in function calling Date: Thu, 11 Jul 2002 05:06:00 -0000 [thread overview] Message-ID: <20020711120255.21903.qmail@sources.redhat.com> (raw) >Number: 7273 >Category: c >Synopsis: having problem with pointer to pointer with const in function calling >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Thu Jul 11 05:06:02 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Pradeep S >Release: gcc 2.95.3 suse linux 7.2 build >Organization: >Environment: suse linux 7.2 >Description: i have a function of following kind. Which means to my understanding, ppi is a pointer to pointer to constant integer. ie (**ppi cannot be modified). void func(const int **ppi) { } i tried to call this function like this int main() { int **ppi; //some initialization of ppi stuff func(ppi); return 1; } when i compile this, i am getting a warning, which i feel wrong. it says argument has pointer type mismatch. i am passing a modifiable data to a function which will not modify the data(hence const, in the hope that in future it may be passed some constant, which does happen in my code). can u tell a scenario in which this can lead to disaster? so, what does the warning signify? similarly when formal argument is of type int *const **pppi; and actual argument is of type int ***pppi; it says a warning. but it didnot say anything when formal argument is int *const *ppi and actual argument is int **ppi what is the diff in above three cases that causes first two to throw a warning while third compiled quitely? am i bugging u too much? >How-To-Repeat: not appilcaple >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-07-11 12:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-11 5:06 send2pradeep [this message] 2002-07-11 5:27 paolo
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=20020711120255.21903.qmail@sources.redhat.com \ --to=send2pradeep@yahoo.com \ --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).