How to locate cause of deprecation warning?

[Josef Sachs]

What is the easiest way for me to locate in the source code
the cause of a depraction warning? Some deprecation warnings
actually give the file name and line number.

AWS-Sachs-Ubuntu$ usr/bin/julia -e "using Gallium"
INFO: Recompiling stale cache file /home/sachs/.julia/lib/v0.5/Gallium.ji for module Gallium.

WARNING: deprecated syntax "[a=>b for (a,b) in c]".
Use "Dict(a=>b for (a,b) in c)" instead.

[daycaster]

Have you discovered the joys of Lint.jl ? (https://github.com/tonyhffong/Lint.jl). I've found it pretty useful in the past, although I don't know how up to date it is at the moment.

[Josef Sachs]

>>>>> On Thu, 16 Jun 2016 04:34:36 -0700 (PDT), <dayc...@icloud.com> said:

> Have you discovered the joys of Lint.jl ? (https://github.com/tonyhffong/Lint.jl). I've found it pretty useful in the past, although I don't know how up to date it is at the moment.

I've been meaning to try it, but didn't get around to it until now.

It appears that Lint.jl does not currently support v0.5.
Too early to submit a GitHub issue for that?

I should probably submit a feature request (GitHub issue) for
syntax deprecations to report file names and line numbers.

[Tony Kelman]

Deprecation warnings are supposed to be reporting filename and line number, I think anywhere they don't is likely a bug.

[Tim Holy]

Many of them do already, but there are still some holes. If you have a clear
example where it fails to print a line number, that would make a great issue.

In some circumstances https://github.com/timholy/
DebuggingUtilities.jl#test_showline might be helpful?

--Tim