public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Rafal Dabrowa" <rdabrowa@poczta.onet.pl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7008: unexpected error message "var was not declared in this scope" Date: Sun, 14 Jul 2002 04:56:00 -0000 [thread overview] Message-ID: <20020714115600.10399.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7008; it has been noted by GNATS. From: "Rafal Dabrowa" <rdabrowa@poczta.onet.pl> To: <rdabrowa@poczta.onet.pl>, <gcc-gnats@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org> Cc: Subject: Re: c++/7008: unexpected error message "var was not declared in this scope" Date: Sun, 14 Jul 2002 13:58:10 +0200 I have a few additional remarks about compiler behavior. Compiler should not take a global variable because use of local one is forbidden. This is unclear and confusing people. Compiler should put an error message instead. Consider the following code: const int N = 500; void f(int var) { const int N = 5; struct { char str[N]; } z1; // error: use of local variable is forbidden here struct { char str[::N]; } z2; // global variable used, ok } Also, error text: "var was not declared in this scope" is unclear, too. In my opinion, better is such like "use of local variable is not allowed here". Rafal Dabrowa
next reply other threads:[~2002-07-14 11:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-14 4:56 Rafal Dabrowa [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-13 2:41 lerdsuwa 2002-07-12 23:06 Rafal Dabrowa 2002-07-11 7:39 lerdsuwa 2002-06-12 13:16 rdabrowa
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=20020714115600.10399.qmail@sources.redhat.com \ --to=rdabrowa@poczta.onet.pl \ --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).