Clojure JIRA

Clojure JIRA http://dev.clojure.org/jira This file is an XML representation of an issue en-us

4.4

649

25-07-2011

[CLJ-272] load/ns/require/use overhaul http://dev.clojure.org/jira/browse/CLJ-272 Clojure <p>Creating this ticket to describe various things people have wanted to change about how ns works:</p> <h2><a name="Minimalneeds"></a>Minimal needs </h2> <ol> <li>there should be a primitive level of loading (presumably <tt>load</tt>) that just loads without question.</li> <li>the api should be unified across the ns and direct forms. No more keywords or quoting! So <tt>(use foo)</code> not <code>(use 'foo)</code>. This makes <code>use</code> et al macros, so there should also be new fn versions (maybe <code>use*</tt>).</li> </ol> <h2><a name="Otherpossibilitiestodiscuss."></a>Other possibilities to discuss.</h2> <ol> <li>Feature addressing the {{:like</code> and <code>:clone</code> ideas from <a href="http://onclojure.com/2010/02/17/managing-namespaces/">http://onclojure.com/2010/02/17/managing-namespaces/</a>. I think I would prefer a single new option <code>:clone</code> which allows <code>:only</code> and <code>:exclude}} features as subspecifiers.</li> <li>Convenience fn to unmap all names in a namespace?</li> </ol> CLJ-272

load/ns/require/use overhaul

Enhancement Open Unresolved Unassigned None Thu, 18 Feb 2010 03:47:00 -0600 Tue, 28 Feb 2012 03:56:11 -0600 Backlog 3 6 <p>Converted from <a href="http://www.assembla.com/spaces/clojure/tickets/272">http://www.assembla.com/spaces/clojure/tickets/272</a></p> <p>stu said: Suggestions from Volkan Yazici:</p> <p>Hi,</p> <p>I saw your "load/ns/require/use overhaul" ticket<span class="error">[1]</span> and would like to<br/> ask for a few extra overhaulings. I have a project called retop, and<br/> here is its file hiearachy:</p> <p> tr/edu/bilkent/cs/retop.clj<br/> tr/edu/bilkent/cs/retop/km.clj<br/> tr/edu/bilkent/cs/retop/graph.clj<br/> tr/edu/bilkent/cs/retop/main.clj<br/> tr/edu/bilkent/cs/retop/util.clj</p> <p>In retop.clj, I have below ns definition.</p> <p> (ns tr.edu.bilkent.cs.retop<br/> (:gen-class)<br/> (:import<br/> (com.sun.jna<br/> Function<br/> Pointer)<br/> (com.sun.jna.ptr<br/> IntByReference)<br/> (tr.edu.bilkent.cs.patoh<br/> HyperGraph<br/> HyperGraphException<br/> Parititoning<br/> ParititoningParameters))<br/> (:load<br/> "retop/util"<br/> "retop/km"<br/> "retop/graph"<br/> "retop/main"))</p> <p>And in every .clj file in retop/ directory I have below in-ns in the<br/> very first line.</p> <p> (in-ns 'tr.edu.bilkent.cs.retop)</p> <p>The problems with the ns decleration are:</p> <p>1) Most of the :import's in retop.clj only belong to a single .clj file.<br/> For instance,</p> <p> (tr.edu.bilkent.cs.patoh<br/> HyperGraph<br/> HyperGraphException<br/> Parititoning<br/> ParititoningParameters)</p> <p> imports are only used by graph.clj. Yep, I can add an (import ...)<br/> line just after the (in-ns ...), but wouldn't it be better if I can<br/> specify that in (in-ns ...) form?</p> <p>2) See (:load ...) clause in (ns ...) form. There are lots of<br/> unnecessary directory prefixes. I'd be prefer something ala Common<br/> Lisp's defpackage:</p> <p> (:load<br/> "packages" ; packages.clj<br/> ("retop"<br/> "util" ; retop/util.clj<br/> "km" ; retop/km.clj<br/> "graph" ; retop/graph.clj<br/> ("graph"<br/> "foo" ; retop/graph/foo.clj<br/> "bar) ; retop/graph/bar.clj<br/> "main")) ; retop/main.clj</p> <p> Also, being able to use wildcards would be awesome.</p> <p>3) There are inconsistencies between macros and functions. For instance,<br/> consider:</p> <p> (ns foo.bar.baz (:use mov))<br/> (in-ns 'foo.bar.baz)<br/> (use 'mov)</p> <p> I'd like to get rid of quotations in both cases.</p> <p>I'm not sure if I'm using the right tools and doing the right approach<br/> for such a project. But if you agree with the above overhauling<br/> requirements, I'd like to see them appear in the same assembla ticket as<br/> well.</p> <p>stuart.sierra said: My requests:</p> <p>1. If writing macros that do not evaluate their arguments, provide function versions that do evaluate their arguments.</p> <p>2. Do not support prefix lists for loading Clojure namespaces. It's hard to parse with external tools.</p> <p>3. Do not conflate importing Java classes with loading Clojure namespaces. They are fundamentally different operations with different semantics.</p> <p>I have implemented some ideas in a macro called "need" at <a href="http://github.com/stuartsierra/need">http://github.com/stuartsierra/need</a></p> <p>Further requests:</p> <p>Permit tools to read the "ns" declaration and statically determine the dependencies of a namespace, without evaluating any code.</p> <blockquote><p>Permit tools to read the "ns" declaration and statically determine the dependencies of a namespace, without evaluating any code.</p></blockquote> <p>This would be great for building OSGi bundles where Bnd is currently not much help.</p> Global Rank