public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@net.local>
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: other/9071: Warning for blocks not closed in same file as opened in
Date: Fri, 27 Dec 2002 15:36:00 -0000	[thread overview]
Message-ID: <E18S3sW-0003i1-00@tango.net.local> (raw)


>Number:         9071
>Category:       other
>Synopsis:       Warning for blocks not closed in same file as opened in
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 27 15:36:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Anthony DeRobertis <asd@suespammers.org>
>Release:        3.2.1 (Debian) (Debian unstable)
>Organization:
The Debian Project
>Environment:
System: Debian GNU/Linux (unstable)
Architecture: i686
host: i386-linux
Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-objc-gc i386-linux
Thread model: posix
gcc version 3.2.2 20021212 (Debian prerelease)
>Description:
[ Reported to the Debian BTS as report #122103.
  Please CC 122103@bugs.debian.org on replies.
  Log of report can be found at http://bugs.debian.org/122103 ]
	

Accidentally leaving the close brace off of a block in e.g., a header
file will often result in errors in files that include it, without any
indication of what is wrong. For example, leaving a namespace open will
usually just give a parse error at the end of the including file.

I'd appreciate it if a warning were issued at the end of a file if there
are still any blocks open.

I realize that leaving a block open through a file ending is not a
violation of the ISO standard's letter or spirit; however, I believe it
is usually a mistake, and one that is otherwise hard to track down. A
compiler warning would make tracking it down much easier, and is
unlikely to give any false alarms.


>How-To-Repeat:
	
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-12-27 23:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E18S3sW-0003i1-00@tango.net.local \
    --to=doko@net.local \
    --cc=122103@bugs.debian.org \
    --cc=debian-gcc@lists.debian.org \
    --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: 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).