Package: g++-3.0 Version: 1:3.0.2-3 Severity: wishlist -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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. - -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux bohr 2.4.16 #2 SMP Wed Nov 28 05:25:00 EST 2001 i686 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages g++-3.0 depends on: ii gcc-3.0 1:3.0.2-3 The GNU C compiler. ii gcc-3.0-base 1:3.0.2-3 The GNU Compiler Collection (base ii libc6 2.2.4-5 GNU C Library: Shared libraries an ii libstdc++3-dev 1:3.0.2-3 The GNU stdc++ library version 3 ( -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8Ci7S5lsmI6uA7bQRAvfkAJ42N2/3M+lpiPmqFzK9xPN8XQSaIgCePy3A nnESs3UUazVoA2AcfpUK72I= =3kIg -----END PGP SIGNATURE-----
