I was thinking of writing a poor man's enclojure (to get a feel for a
real clojure project). Looks like a lot of work is already done :)
I see many references to clojure contrib, perhaps this jar could be
made more prominent on clojure.org?
On Dec 30, 5:40 pm, Chouser wrote:
> On Tue, Dec 30,
Makes sense, thanks
On Dec 30, 5:29 pm, pmf wrote:
> On Dec 30, 11:08 pm, falcon wrote:
>
> > Impressive, source file and line numbers are already included!
> > I need to better understand reader macro (or where ever # comes from).
>
> You actually need to know two things regarding this issue.
On Tue, Dec 30, 2008 at 4:29 PM, falcon wrote:
>
> Generally speaking, how can I get information about my environment:
> -which bindings exist
> -the source code for a given function (if source code is available)
pmf's explanations are solid, but for the source code in particular,
you may be int
On Dec 30, 11:08 pm, falcon wrote:
> Impressive, source file and line numbers are already included!
> I need to better understand reader macro (or where ever # comes from).
You actually need to know two things regarding this issue.
In function-definitions, the meta-data is actually assigned to
Impressive, source file and line numbers are already included!
I need to better understand reader macro (or where ever # comes from).
Thanks
>
> Be sure to var-quote the function, i.e. don't use (meta print), but
> (meta #'print).
--~--~-~--~~~---~--~~
You receiv
On Dec 30, 10:29 pm, falcon wrote:
> (doc fn) gives me a description of the function, and information about
> function arity. I assumed the description and arity were part of
> metadata but (meta fn) only returns nil (for a few functions I tried).
Be sure to var-quote the function, i.e. don't
How do I find the arity of a given function?
I can get a list of all name spaces using
(all-ns)
I can get functions within each name space using
(find-ns 'clojure) ; so map find-ns over each value returned by all-ns
(doc fn) gives me a description of the function, and information about
function
