This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/17026] Error at last empty case in switch block.
- From: "jsm at polyomino dot org dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Aug 2004 15:01:02 -0000
- Subject: [Bug c/17026] Error at last empty case in switch block.
- References: <20040814134606.17026.do8896@db.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From jsm at polyomino dot org dot uk 2004-08-14 15:01 -------
Subject: Re: New: Error at last empty case in switch block.
On Sat, 14 Aug 2004, do8896 at db dot com wrote:
> Those code-constructions meets in libgda and libgnome-db( and may be all of this
> codes normally compiled under older versions of gcc)
This undocumented extension was deprecated (with a mandatory warning when
it was used) in 3.0, released June 18, 2001, and removed in 3.4.0,
released April 18, 2004. How long would you expect undocumented
extensions to be deprecated before being removed, if nearly three years
isn't enough? The normal period for most deprecations is a single release
(e.g. deprecate in 3.3 and remove in 3.4), which allows about a year for
people to see and fix the warnings, but undocumented extensions are
subject to change and removal without deprecation period - indeed, removal
by accident if someone didn't realise they were part of the extended
language. The ease of fixing - in this case, by adding a single semicolon
- is a relevant factor in deprecation; we simply didn't happen to get
round to removing this extension until 3.4 though removal in 3.1 would
have been reasonable.
http://gcc.gnu.org/gcc-3.0/caveats.html
http://gcc.gnu.org/gcc-3.4/changes.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17026