Hi,
I just had the same problem and discovered it was a cyclic dependency
- maybe you want to check for that, too..
Regards Benjamin
On Jan 3, 9:19 am, Praki wrote:
> Hi,
>
> I have a silly problem compiling my cljs files. I have to run the
> cljsc command twice in succession to generate javasc
Hi,
this should be what you need:
http://stackoverflow.com/questions/4690758/splitting-a-clojure-namespace-over-multiple-files
On Jun 18, 3:52 pm, Matt Mitchell wrote:
> Hi,
>
> I have 3 namespaces, each with functions that relate to the name of the ns:
>
> core -- contains config and *server* v
Some remarks:
> (defmacro make-msg-ewrapper [method-names]
maybe use [& method-names] so people can write (make-msg-wrapper a-
method-name another-method-name)
> `(proxy [EWrapper] []
> ~@(map
> (fn [method-name]
> (let [args (gensym "args")]
this line seems completely us
As a user coming from Haskell, I've always been disturbed by Clojure's
C-like behavior at this point, so I'd agree with the OP. And of course
the solution is not just reverse, as any order should be possible.
The question is how one could implement this without raising more
problems. Maybe a strat
Ok, I think I've got it - so basically all private variants should go
in contrib now and moving defn- now would break a lot of people's code
"just" for a little more coherency.
But in this case, I'd like def- to be included in clojure.contrib.def.
I dislike defvar as it's just name and docstring p
wrote:>> Please don't. It has already been
discussed and declined. The metadata is uglier because we want doing
this to be slightly ugly..
Sorry, didn't get your response in time..
Anyways, I agree with Ken it seems weird to have defn- in core and not
def- - or is defn- sort of deprecated in favo
I think a def- definitely belongs in core for consistency reasons.
So I'm writing a ticket and patch now.
Cheers, Benjamin
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts f
I guess it was Rich's intention to have swap! be used for real atoms
only so your code remains understandable - that's why it's called
swap! for atoms, alter for refs and alter-var-root for vars.
So why not define your own protocol for updating documents? If you
really want (usually bad idea, I gu
Hi,
I'm recently having problems where leiningen hangs for like 20
secondes after everything is done (I've added print statements to a
custom task, so I'm pretty sure nothing has to be done anymore). I'm
using Mac OS Snow Leopard, but a friend of mine is experiencing the
same with Ubuntu.
Did any
Hi,
> We could promote defvar from clojure.contrib.def?
I don't like defvar having the docstring last, while all other
definers have them directly after the name - this should be
consistent.
Also, I think the default-def should be "the right and good one" -
because def is just the best name. Eve
Hi,
I think def should support docstrings, as ^{:doc "foo"} is 8
characters longer then "foo" - not to mention consistency across
definers as well as readability. Therefore, I created a ticket and
patch at
http://www.assembla.com/spaces/clojure/tickets/280-def-should-support-an-optional-doc-strin
I'm using the following workaround for now:
- remove clojure-snapshots from the secttion of the
pom.xml
- delete all jar's that are "too new" (guess sth. near the end of
april) from maven_repository/org/clojure/clojure/1.2.0-master-SNAPSHOT
- be happy
This works as without the repository-declar
Hi nipra,
and which swank-clojure do you use on the emacs side? I guess not the
one from ELPA, right?
Cheers,
Benjamin
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from
Hi,
I think many people (including me) have the problem that ELPA-swank
uses clojure's old ^-syntax and therefore breaks with clojure-1.2.0-
master-SNAPSHOT
Does anyone have a plan what I can do assuming I want to keep both the
new clojure version and swank?
I'm using Maven, if that matters.
Che
> > (def *assert* false)
>
> You cannot use def to change the value of a var in another namespace.
> This is nothing specific to *assert* or to clojure.core.
> Here is what you can do instead:
>
> (alter-var-root (var *assert*) (fn [_] false))
I actually tried from inside clojure.core,
Hi!
Yesterday on IRC some of us were struggling with the usage of
dynamically rebound vars inside macros which led to interesting
compile vs run time issues. I've got some questions for the experts at
the very bottom of this post - but before I'd like to explai this
issue for the less experienced
+1 for debugging (through swank-clojure, I hope)
besides, rolling your own leiningen plugins
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated
17 matches
Mail list logo