http://d.puremagic.com/issues/show_bug.cgi?id=199
--- Comment #32 from Nick Treleaven <[email protected]> 2013-06-06 05:20:21 PDT --- (In reply to comment #31) > >> The (imo correct) path is that the NoScopeStatment should still > >> provide no scope, but emit a deprecated message if anything > >> declared in the scope is used. > > If you're going to go as far as that, why not emit a deprecation message if > any > declarations appear in it at all? That sounds easier to implement, and IMO is a bit better than deprecating having a non-empty block after a label. We would also need to deprecate having scope() statements in a labelled block. Bug 827 would also need a solution. comment #30: > I understand your position, but deprecation really implies that something WILL > be removed, and usage NEEDS to stop. Having something permanently deprecated > is > not tenable: there is a compile mode that makes deprecated calls errors, and > here, it is not an error. If a user has chosen to enable deprecation errors, that is their problem IMO. By default the code would not break. Note: GTK2 kept its deprecated symbols until GTK3, rather than scheduling removal at a certain date. Anyway, a limited period of deprecation rather than just changing behaviour might be a good compromise. Perhaps 2 years? -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
