Thanks all, folks. Rich's video helped tremendously. The a-ha moment was
the realization that the biggest reason to abstract data access in Java is
the non-uniform built-in access to data: accessing fields in objects is
different from hashmaps which is different from instance access which is
Can anyone explain this change?
(clojure-version) => "1.2.0"
(let [x 8.9] (identical? x x)) => true
Compared to:
(clojure-version) => "1.4.0"
(let [x 8.9] (identical? x x)) => false
Thanks.
David Sletten
--
You received this message because you are subscribed to the Google
On Sat May 5 14:53 2012, David Sletten wrote:
> Can anyone explain this change?
> (clojure-version) => "1.2.0"
> (let [x 8.9] (identical? x x)) => true
>
> Compared to:
> (clojure-version) => "1.4.0"
> (let [x 8.9] (identical? x x)) => false
Well, this is certainly an interesting phenomenon.
On May 5, 2012, at 3:06 PM, Daniel Solano Gómez wrote:
> On Sat May 5 14:53 2012, David Sletten wrote:
>> Can anyone explain this change?
>> (clojure-version) => "1.2.0"
>> (let [x 8.9] (identical? x x)) => true
>>
>> Compared to:
>> (clojure-version) => "1.4.0"
>> (let [x 8.9] (identical? x
On Sat May 5 16:43 2012, David Sletten wrote:
> Thanks for your response Daniel. You explain WHAT is apparently
> happening here. However, I am still struggling to understand WHY this
> is the new behavior.
Yes, this is indeed a valid question. I think the answer is that this
particular behavio
Fantastic Daniel. Your thorough analysis has cleared up my confusion. I see now
that Java is partly to blame for this idiosyncratic behavior.
Furthermore, I agree that this is a relatively unlikely use of 'identical?'.
Considering all of the usual concerns when comparing floating-point numbers,
I'm attempting to start a swank-clojure session within a grails
application. This part is easy and works fine. However, whenever I change
a groovy class clojure does not see this change until I restart the jvm. I
mucked around a bit with classlojure and pomegranate trying to figure out
if I
Hi, my project.clj contains
:dependencies [[org.clojure/clojure "1.4.0"]
[noir-cljs "0.3.0"]
[jayq "0.1.0-alpha1"]
[fetch "0.1.0-alpha2"]
[crate "0.1.0-alpha3"]
[noir "1.3.0-beta2"]]
but 'lein deps' does not do
When i first upgraded to clojure 1.4 i had a similar issue with lein not
downloading updated dependencies. It tirned out to be an invalid version range
dependency spec in midje that caused it to fail silently. Perhaps try removing
all other dependencies first and try again.
--
You received th
> i need a more basic guidence on how to install the nessecery plugins
> to eclipse, and what to do with them...
eclipse IDE may look like a good idea but in the beginning it just
increases the amount of work you need to do and troubles you need to
overcome. Just start with the REPL and any reason
I put
:dev-dependencies [[clj-ns-browser "1.2.0"]]
to my project.clj and did:
$ lein deps
Copying 46 files to /home/bost/dev/webcli/lib
[WARNING] Overriding profile: 'null' (source: pom) with new instance
from source: pom
[WARNING] Overriding profile: 'null' (source: pom) with new instance
from
On 06/05/12 00:51, Rostislav Svoboda wrote:
i need a more basic guidence on how to install the nessecery plugins
to eclipse, and what to do with them...
eclipse IDE may look like a good idea but in the beginning it just
increases the amount of work you need to do and troubles you need to
overcom
On May 5, 2012, at 6:37 PM, Kurt Harriger wrote:
> When i first upgraded to clojure 1.4 i had a similar issue with lein not
> downloading updated dependencies. It tirned out to be an invalid version
> range dependency spec in midje that caused it to fail silently. Perhaps try
> removing all ot
On 6 May 2012 01:37, Kurt Harriger wrote:
> When i first upgraded to clojure 1.4 i had a similar issue with lein not
> downloading updated dependencies. It tirned out to be an invalid version
> range dependency spec in midje that caused it to fail silently. Perhaps try
> removing all other depe
Rostislav Svoboda:
> My guess is that any of the dependencies I defined in my project.clj contains
>:dependencies [[org.clojure/clojure "1.3.0"] ... ]
> so it overrides my [org.clojure/clojure "1.4.0"]
You can exclude org.clojure/clojure for your dependencies:
https://github.com/michaelklish
On May 5, 2012, at 7:38 PM, Rostislav Svoboda wrote:
> My guess is that any of the dependencies I defined in my project.clj contains
>:dependencies [[org.clojure/clojure "1.3.0"] ... ]
> so it overrides my [org.clojure/clojure "1.4.0"]
If you have Leiningen 2, you can find the culprit like t
Guys, I need to thank you both. Now it works:
:dependencies [
[org.clojure/clojure "1.4.0"]
[colorize "0.1.1" :exclusions [org.clojure/clojure]]
[noir-cljs "0.3.0"]
[jayq "0.1.0-alpha1"]
[fetch "0.1.0-alpha2"]
17 matches
Mail list logo
