Hi Sean,
Lein 2.3.2 fixed #1150 and #1292 on Windows, tested on Windows 7 and
Windows XP. Is there any particular issue# your use case relates to? Please
mention/file the issues -- I will see if I can find a fix.
Shantanu
On Wednesday, 21 August 2013 10:43:36 UTC+5:30, Sean Corfield wrote:
>
>
Yup, I've done OOP in the past but probably even closer procedural
programming. Recently I've been working pretty much exclusively in
python/C++ which are somewhat at two extremes. I'm hoping to see Clojure to
be a blend of these two and a replacement especially in areas where things
in python are
On Tue, Aug 20, 2013 at 9:31 PM, Kuba Roth wrote:
> The reason I looked into 'intern' can only be explained by totally lack of
> experience in Clojure and more general functional programming.
Ah, is your background OOP?
You'll find the functional world is pretty different. No "variables"
in the
Upgrading on Mac/Linux was painless as usual - and everything here
seems to run fine with 2.3.2 - but Windows continues to be a pain in
the rear...
You can't lein upgrade so I updated the version string in lein.bat and
tried lein self-install:
C:\Users\Sean>lein self-install
Downloading Leiningen
Thanks Sean, your example looks much cleaner and most important works!
The reason I looked into 'intern' can only be explained by totally lack of
experience in Clojure and more general functional programming.
My goal was to dynamically create a var inside the 'doseq' and apparently
'intern' is
Your example could be written:
(-> foo
bar
(baz quuz)
blah)
But I suspect you meant something like this:
(-> foo
bar
(as-> <> (baz whiz <> quuz))
blah)
In other words, you use as-> with -> for just those cases where you
need something that isn't in the first or last argu
There's a way to reconcile all of this: if you treat the "environment as a
value" then I believe you can achieve both:
- Incremental REPL-style commands that work immediately in the current
environment
- Arbitrary declaration order in files
>From a technical perspective, the environment would c
Second- that would be a nice, and intuitive, enhancement.
---
Joseph Smith
j...@uwcreations.com
@solussd
> On Aug 20, 2013, at 8:52 PM, Ken Restivo wrote:
>
> I like the as-> macro, mostly because it'd theoretically obviate the need to
> include the Swiss Arrows library anymore.
>
> There's
I like the as-> macro, mostly because it'd theoretically obviate the need to
include the Swiss Arrows library anymore.
There's one reason why I keep going back to Swiss Arrows though: the ability to
include single-arg functions in the chain that do not have the explicit token.
i.e. in Swiss Arr
Very likely Juan, as seen here:
(let [agents (map agent (range 30 35))]
(doseq [a agents]
(send a + 100)
(println @a))
(doseq [a agents]
(println @a)))
For me that prints:
30
31
32
33
34
130
131
132
133
134
but I suspect that's more luck that anything since there's no reason
the
If on the *println* you don't see the value updated, it's probably because
the operation sent to the agent wasn't applied yet.
Add a *(Thread/sleep 500)* in between the *send *and *println *expressions
and you'll see the expected agents'.
Cheers,
JF
On Wednesday, August 21, 2013 12:21:59 A
A core.async implementation of Per Brinch Hansen, "Parallel Cellular
Automata" (1992):
https://github.com/nodename/async-plgd#cellular
--
--
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
N
Hi there,
I've got a range of values and I'd like to run agents for each value per
thread. For some reason I've got only one agents being updated.
Not sure what's wrong here but I suspect must be doing something terrible
stupid...
Thanks!
(doseq [s (range 30 35)]
;(println (format "_%
David Pollak writes:
> I have an application where I need multiple independent Clojure contexts
> running in the same JVM.
You can use ShimDandy[1] to load multiple Clojure runtimes in the same
JVM, and call into those runtimes from Java. That's what Immutant[2] and
the Clojure language module f
Hello everybody.
I'm happy to announce the release of Leiningen 2.3.2, a minor bugfix
release over 2.3.1. Changes include the following:
* Write `.nrepl-port` file for better tool interoperability. (Phil Hagelberg)
* Support targeted upgrades in `lein.bat`. (Shantanu Kumar)
* Warn when projects
David Pollak writes:
> I have an application where I need multiple independent Clojure contexts
> running in the same JVM.
Classlojure [1] can do this for you, taking care of correct
initialisation, and evaluation.
[1] https://github.com/flatland/classlojure
pgpjGCdyjK4nh.pgp
Description: PGP
Sean,
Thanks for the response.
The issues that I've come across using code similar to yours is that if
there are two people sharing the same namespace, they will over-write each
others' stuff.
I guess I'll wait for 1.6 unless others have ideas.
Thanks,
David
On Tue, Aug 20, 2013 at 1:55 PM
Just FYI (and you probably already know this David), most of the
clojure.lang.RT class is considered an implementation detail and is
subject to change without notice. I believe 1.6 will bring a new API
that is intended to provide a supported way to embed Clojure into
JVM-based applications.
Based
Howdy,
I have an application where I need multiple independent Clojure contexts
running in the same JVM.
I've played around with a custom classloader, but when I try to eval code
(calling RT.eval.invoke via reflection), I wind up with:
java.lang.ClassCastException: clojure.core$eval1 cannot be c
Hi all,
I've just uploaded iniconfig 0.2.0 to Clojars.
iniconfig is minimal Clojure library designed to read ini files. It uses
the number sign '#' as comment character and allows multi-line values.
iniconfig and it's documentation can be found on github:
https://github.com/brainbot-com/clj-in
Sorry, I meant:
(go (let [foo (http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For
Hi, y'all.
I'm having trouble with core.async in ClojureScript.
Inside 'let forms in 'go blocks, making calls to namespaced functions
causes the compiler to die with an IndexOutOfBoundsException.
For example:
(ns my-ns
(:require [bar]))
(go (let [foo (bar/baz 1 2 3)]
(.log js/console foo)))
Hi all,
I've a rather strange problem...I know that all clojure collections
implement Serializable but when I try to use standard Java serialization
on a vector of records I get this exception:
/NotSerializableException clojure.core.Vec
java.io.ObjectOutputStream.writeObject0 (ObjectOutputSt
>
> That's what I was referring to. Was there something specific about it
> that you wanted to call out? :)
>
Nope; just wanted to bring it up.
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@google
Nice! Thanx. More stuff for me to read / play with in my "copious free time" :)
Sean
On Tue, Aug 20, 2013 at 9:48 AM, Jim Crossley wrote:
> Here you go, Sean: http://immutant.org/news/2013/08/20/openshift-clustering/
>
> Feedback appreciated!
>
> Jim
>
>
> On Thursday, August 1, 2013 1:22:05 PM
REPL versus compilation in Lisp have for many decades been two different
things.
In the REPL, you were allowed to refer to symbols that were undefined in the
current
lexical scope, hoping that at runtime they would eventually exists some where
on the stack.
To compile such code you needed to ad
Here you go, Sean: http://immutant.org/news/2013/08/20/openshift-clustering/
Feedback appreciated!
Jim
On Thursday, August 1, 2013 1:22:05 PM UTC-4, Sean Corfield wrote:
>
> Great news! Every conference I've been to lately, I've been bugging
> the OpenShift guys - I know they have been rewritin
Hi Steve, this is great for us n00bs. Thank you!
On Aug 19, 2013, at 9:10 AM, Steve Shogren wrote:
> http://deliberate-software.com/intro-to-macros/
>
> I wrote this tutorial up for a friend of mine who is a Ruby programmer
> thinking of learning Clojure, as my defense of why Clojure is worth
Tim Visher writes:
> On Mon, Aug 19, 2013 at 11:09 PM, Armando Blancas wrote:
>>> I'll point out as well that though I thought Yegge's criticisms of
>>> Clojure were a bit polemical (I guess that's his style), the single
>>> pass compiler issue was one of his biggest gripes, and I do think it
>>
On Mon, Aug 19, 2013 at 11:09 PM, Armando Blancas wrote:
>> I'll point out as well that though I thought Yegge's criticisms of
>> Clojure were a bit polemical (I guess that's his style), the single
>> pass compiler issue was one of his biggest gripes, and I do think it
>> still rings true. I feel
A normal function just runs naturally through its code -- it can't
abort/suspend/pause/defer evaluation. (Only the JVM or kernel can suspend
things for you safely.) The inversion of control macros enable such
capabilities for Clojure code while preserving normal semantics. It allows
code to *y
31 matches
Mail list logo
