Hey guys,
I've been working on this for a while, experimenting a lot with possible
implementations of Iteratees in Clojure, the library is more like a proof
of concept (not released yet to clojars).
https://github.com/roman/clj-stream
If you are interested in Iteratees (or trying to understand h
Hi Sean,
> The only problem is when a future version of a dependency introduces a>
> breaking change (which happens quite a lot with relatively new>
> libraries).You are right. hmm which we should choose might be bepend on which
> attitude is conservative or progressive.
Keith> The only way I c
% would work even worse because it doesn't nest. I still think the
whole idea ia a dreadful one, but < would cause problems less often
than other suggestions.
On Dec 28, 10:06 pm, Ambrose Bonnaire-Sergeant
wrote:
> On further thought, it will be a breaking change
>
> (def f 1)
>
> (let [x 1]
>
On further thought, it will be a breaking change
(def f 1)
(let [x 1]
f)
% would work better.
Ambrose
On Thu, Dec 29, 2011 at 2:00 PM, Peter Danenberg wrote:
> Since square brackets have been usurped by vectors, angle brackets
> could be used to approximate M-expressions.
>
> Quoth Ambrose
Since square brackets have been usurped by vectors, angle brackets
could be used to approximate M-expressions.
Quoth Ambrose Bonnaire-Sergeant on Boomtime, the 70th of The Aftermath:
> Why not use f ?
>
> On Thu, Dec 29, 2011 at 12:49 PM, Louis Yu Lu wrote:
>
> > Instead of using overloaded (),
Hi--
The only way I could get the colorized stack-trace was to use M-x
clojure-jack-in.
Normally, I type "lein swank" on a command line, then use M-x slime-connect
from Emacs. This is so that I can see the clojure.tools.logging output.
(I've no idea where it goes when you use clojure-jack-in.
f%x% would probably work outside of #() forms. % is a symbol delimiter.
Ambrose
On Thu, Dec 29, 2011 at 12:56 PM, Ambrose Bonnaire-Sergeant <
abonnaireserge...@gmail.com> wrote:
> Why not use f ?
>
>
> On Thu, Dec 29, 2011 at 12:49 PM, Louis Yu Lu wrote:
>
>> Instead of using overloaded (), may
Why not use f ?
On Thu, Dec 29, 2011 at 12:49 PM, Louis Yu Lu wrote:
> Instead of using overloaded (), may be f[x] will cause less trouble,
> and more inline with clojure's syntax as [ ] already being used for
> defining the arguments of the function.
>
> Louis
>
> On Dec 27, 5:26 pm, Gert Verho
Instead of using overloaded (), may be f[x] will cause less trouble,
and more inline with clojure's syntax as [ ] already being used for
defining the arguments of the function.
Louis
On Dec 27, 5:26 pm, Gert Verhoog wrote:
> On 26/12/2011, at 6:23 PM, Louis Yu Lu wrote:
>
> > My proposition is e
On Wed, Dec 28, 2011 at 6:43 PM, Takahiro wrote:
> I think ring should specify dependency using version range like below.
> [clj-stacktrace "[0.2.2,)"] ;; 0.2.2 <= x
>
> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
> I didn't know it until recently, but now I
Hi,
I don't get colored stacktrace.
http://imgur.com/5NCEW
Is any procedure needed?
I've tried 1.3.4 with clojure 1.2.1/1.3.0 and Emacs 23.3.
My .emacs.el includes only load-path and marmalade settings.
>> including [ring "1.0.1"] in my project.clj, which uses clj-stacktrace
>> 0.2.2 instead of 0.
Have just been trying Clooj out and I have to say, it is really really good!
Thanks Arthur for the neat tool.
I particularly like that the repl interaction is very slick, and how
it takes care of project structure in a very minimalist but clearly
structured way.
--
You received this message becau
This is definitely not a JVM limitation, it is a design choice. There
are lisps that have automatic currying, e.g., Qi (http://
en.wikipedia.org/wiki/Qi_(programming_language)).
I think the main issue, why this is not convenient, is that Clojure
functions tend to accept a variable number of argumen
(+ 3) already has a meaning in Clojure. It's an expression whose
answer is 3. How is Clojure supposed to read your mind and know that
you want the output to be a function there?
Similarly, would (+ 3 2) be 5, or would it be the curried function of
+ applied to 3 and 2 and waiting for more parame
Hi everybody..I've a little question..the way in than clojure
implement curry is affected for the jvm or it is a "Rick
decision" ...in haskell every function accept only one parameter and
if you call a function with >1 parameter it use currying...I feel than
it is really natural and more clean than
Baishampayan Ghose writes:
> On Wed, Dec 28, 2011 at 6:33 AM, Phil Hagelberg wrote:
>> I just pushed out version 1.3.4 of Swank Clojure.
>
> Does it work with Clojure 1.2? What exclusions do I need for that in
> my project.clj?
I'm not aware of any issues with using Swank Clojure in 1.2. If you
Gert Verhoog writes:
> On 28/12/2011, at 2:03 PM, Phil Hagelberg wrote:
>> I just pushed out version 1.3.4 of Swank Clojure.
>
> Great stuff, thanks! I ran into the problem with an older
> clj-stacktrace jar as you describe in the documentation, because I'm
> including [ring "1.0.1"] in my projec
On Wed, Dec 28, 2011 at 7:50 AM, jayvandal wrote:
> Doesn't this line of your example run as test?
> user=> (ns jay.test (:require [clojure.contrib.sql :as sql]))
It's just declaring a namespace and requiring clojure.contrib.sql
(which loads the library). I called it jay.test because it was a te
Quoth Louis Yu Lu on Boomtime, the 70th of The Aftermath:
> The proposed syntax sugar apparently pleases my eyes and fingers
> from conventional languages. With some experiments, I found the code
> is more readable for me to use f(x) notation for function call, and
> (op x) for operator.
It sounds
Doesn't this line of your example run as test?
user=> (ns jay.test (:require [clojure.contrib.sql :as sql]))
=
The other code I listed was code to run as a clojure program , not as
leiningen, which you said was missing lines of code after the (ns
I apologize for my lack of understanding
Finally I have considered your advice and namespaced the keywords.
Thanks,
Juan Manuel
>
El miércoles 28 de diciembre de 2011 12:33:22 UTC+1, Meikel Brandmeyer
(kotarak) escribió:
>
> Hi,
>
> Am 28.12.2011 um 11:09 schrieb JuanManuel Gimeno Illa:
>
> > My main concern is that when using reader
Hi,
Am 28.12.2011 um 11:09 schrieb JuanManuel Gimeno Illa:
> My main concern is that when using reader macros for metadata I have to fully
> qualify it. For instance, I must write:
>
> (defdatatype
> ::Streams
> Nil
>(^:ml.datatypes/lazy Cons elem stream))
>
> instead of
>
> (de
On 28/12/2011, at 2:03 PM, Phil Hagelberg wrote:
> I just pushed out version 1.3.4 of Swank Clojure.
Great stuff, thanks! I ran into the problem with an older clj-stacktrace jar as
you describe in the documentation, because I'm including [ring "1.0.1"] in my
project.clj, which uses clj-stacktra
El miércoles 28 de diciembre de 2011 11:01:16 UTC+1, Ambrose
Bonnaire-Sergeant escribió:
>
> I would recommend sticking with namespaced keywords to avoid clashes with
> var metadata keys.
>
> Remember qualified keywords respect namespace aliasing and ::keyword is
> qualified in the current nam
I would recommend sticking with namespaced keywords to avoid clashes with
var metadata keys.
Remember qualified keywords respect namespace aliasing and ::keyword is
qualified in the current namespace.
These can help making the code more readable.
You could store keywords in vars if namespaced key
El sábado 24 de diciembre de 2011 05:21:33 UTC+1, David Nolen escribió:
>
> I'd like to fully support types/records as they provide significant
> performance benefits.
>
Now I'm not very much interested in performance. I have added the
possibility to define datatypes that use lazy constructor
I've been writing some code which adds some keywords in metadata associated
to vars. Initially I used namespaces keywords to not collide with other
keywords. The problem is that having to namespace these keywords makes the
code, at least, ugly. Is it any consensus in the use of keywords in
meta
On Wed, Dec 28, 2011 at 6:33 AM, Phil Hagelberg wrote:
> I just pushed out version 1.3.4 of Swank Clojure.
Does it work with Clojure 1.2? What exclusions do I need for that in
my project.clj?
Regards,
BG
--
Baishampayan Ghose
b.ghose at gmail.com
--
You received this message because you are
I believe that 0.0.2 is the most current release. By cutting a
release, that bumps the "working snapshot" number up to 0.0.3, but
there have been no changes made since 0.0.2.
--Mark
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this gro
On Tue, Dec 27, 2011 at 12:47 PM, vitalyper wrote:
> Do we have this jar in clojars?
Clojure Contrib is released to Maven Central.
> Searched for it under "math" but could
> not find it.
http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.clojure%22%20AND%20a%3A%22math.combinatorics%22
--
Se
30 matches
Mail list logo
