>Submitter-Id: net >Originator: Anthony DeRobertis <[EMAIL PROTECTED]> >Organization: The Debian Project >Confidential: no >Synopsis: >Severity: non-critical >Priority: low >Category: other >Class: change-request >Release: 3.2.1 (Debian) (Debian unstable) >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 [EMAIL PROTECTED] 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: