"Jonathan M Davis" <[email protected]> wrote in message news:mailman.1522.1310360091.14074.digitalmars-d-annou...@puremagic.com...
> With that implemented, it would fix the problem for functions, but I'm not > sure > that it would fix the problem for modules. That would depend on how it was > implemented. As it stands, if you deprecate an entire module, you end up > doing > something like > > deprecated: > > at the top of the module, which is then going to complain about each > symbol in > the model individually when you use it. Ideally, you could make it > complain > about the module when it's imported (and then maybe the specific functions > on > top of that), and that syntax doesn't really give you that. It just makes > it > complain about the symbols when you use them. But that can work too. Ok, would this be fixed by allowing: deprecated module mymodule; and the rest of it?
