http://d.puremagic.com/issues/show_bug.cgi?id=9289
--- Comment #24 from Leandro Lucarella <[email protected]> 2013-02-26 03:38:50 PST --- Woops! I wanted to commit only the title change... (In reply to comment #22) > Such code might, or might not be a use of a deprecated feature. There is no > way > to tell. The patch moves it from "assume it's never a deprecated feature" to > "assume it's always a deprecated feature". > Effectively, you're changing an accepts-invalid bug to a rejects-valid bug. > It's not an improvement. Again, agreed. > Here's what I think should happen: > > -dXX should give a warning (not an error, not silence), whenever a deprecated > feature is used when errors are gagged. You're talking about a new flag I guess... > In other cases, the existing behaviour (silence) should be preserved. Only when gagged I assume. > Basically I think that with any form of -d option, deprecated features should > never compile without generating a warning (even when errors are gagged). Except for plain -d I guess. That's the original meaning of -d, silence everything. > When -d is not used, it should be as if those features don't exist -- there > should > be no difference between something that is deprecated, vs any other sort of > error. Only when errors are gagged I guess. Otherwise is going back to where we started. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
