[Issue 17906] Deprecated functions should not cause deprecated warnings for using deprecated features

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=17906

--- Comment #4 from FeepingCreature  ---
Huh, seems like you're right. Not sure if this was fixed or it always worked
that way. Either way, good to know!

I guess this bug report is about Mathias Lang's problem now.

--

[Issue 17906] Deprecated functions should not cause deprecated warnings for using deprecated features

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=17906

--- Comment #3 from Mathias Lang  ---
Could you paste the message generated ? In your example, I would expect a
deprecation to be generated for the import, but not on the actual function
declaration.

--

[Issue 17906] Deprecated functions should not cause deprecated warnings for using deprecated features

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=17906

--- Comment #2 from FeepingCreature  ---
That's also true, but my example refers specifically to deprecated functions
using deprecated types. However, I labelled the bug report wrong, and your
example actually fits it better. :)

--

[Issue 17906] Deprecated functions should not cause deprecated warnings for using deprecated features

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=17906

Mathias Lang  changed:

   What|Removed |Added

 CC||mathias.l...@sociomantic.co
   ||m

--- Comment #1 from Mathias Lang  ---
Yeah, put simply, the following code:
```
deprecated void main ()
{
Object o = new Object;
delete o;
}
```

should compile with `dmd -de test.d` (DMD v2.079)

Currently this is done for other deprecated symbols: deprecated functions can
call other deprecated functions, use deprecated types, and a deprecated
aggregate can have fields of deprecated types... So it should be done for
language deprecations as well.

--