http://dev.clojure.org/jira This file is an XML representation of an issue en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/CLJ-706 Clojure <p>From the mailing list <a href="http://groups.google.com/group/clojure/msg/c41d909bd58e4534">http://groups.google.com/group/clojure/msg/c41d909bd58e4534</a>. It is easy to use deprecated namespaces without knowing you are doing so. The documentation warnings are small, and there is no compiler warning.</p> <p>Some possibilities include:</p> <ol> <li>much more visible deprecation styling in the documentation</li> <li>stderr warnings when referencing a deprecated thing.</li> </ol> <p>I don't love the idea of stderr warnings on all the time. Rich: is there an approach to this that you would like to see a patch for?</p> CLJ-706

make use of deprecated namespaces/vars easier to spot

Enhancement Minor Open Unresolved Unassigned Stuart Halloway Wed, 5 Jan 2011 20:39:01 -0600 Wed, 13 Feb 2013 00:38:18 -0600 2 2 <p>I don't mind warning to stderr</p> <p>706-deprecated-var-warning.diff adds warnings when using deprecated vars. The other three patches clean up deprecation warnings.</p> <p>Great stuff. I looked through the first patch, and didn't see anything in there that lets someone disable deprecation warnings from the command line, the way that <b>warn-on-reflection</b> can today be set to true with a command line option.</p> <p>Is that something important to have for deprecation warnings?</p> <p>I was hoping it would be quick and easy to add source file, line, and column info to the deprecation warning messages. It isn't as easy as adding them to the format() call, because the method analyzeSymbol doesn't receive these values as args. Is this deprecation check being done in a place where it is not easy to relate it to the source file, line, and column? Could it be done in a place where that info is easily available?</p> <p>Another patch - this time to warn on loading deprecated namespaces, instead of vars. This patch requires the first one.</p> <p>Re: line/column, I'll figure out how to thread the compile context through if it's desired.</p> <p>Re: Compile flag. I have a patch for this also, but I'm still verifying how to invoke. How is warn-on-reflection set by command line?</p> <p>Re: Compile flag. Don't hold off on implementing a flag if you want to, but it might be worth hearing from others whether such a command line option is even desired. I was asking in hopes of eliciting such a response.</p> <p>For the way that it is handled in the Clojure compiler, search for REFLECTION_WARNING_PROP and related code in Compile.java. If you invoke the Clojure compiler directly via a Java command line, use -Dclojure.compile.warn-on-reflection=true (default is false). See the recent email thread sent to Clojure Dev Google group if you want to know how to do it via ant or Maven. Link: <a href="https://mail.google.com/mail/?shva=1#label/clojure-dev/13aa0e34530196c3">https://mail.google.com/mail/?shva=1#label/clojure-dev/13aa0e34530196c3</a></p> <p>There is also a separate command-line flag called <b>compiler-options</b> (see Compile.java) that is implemented as a map inside the compiler. It was added more recently than <b>warn-on-reflection</b>, and might be the preferred method to add more such options, to avoid having to continue to add more arguments to the pushThreadBindings calls done in several places.</p> <p>Thanks, Andy.</p> <p>Alternately for the last ns patch, it is equivalent to call (print-method msg <b>err</b>), rather than binding <b>out</b> to <b>err</b>, may be more readable. I'll be glad to send that in if it's preferable.</p> <p>706-deprecated-var-warning-patch-v2.txt dated Feb 12 2013 is identical to 706-deprecated-var-warning.diff dated Oct 26 2012, except it applies cleanly to latest master.</p> Global Rank Patch Code