jim wrote:
> I've just posted a tutorial on using monads in Clojure at
>
> http://intensivesystems.net/tutorials/monads_101.html
>
> It's one big chunk of text since I haven't had time to break it up
> yet. It's also kind of rough, so if you see any typos, misspellings,
> errors, etc., post 'em
Chris wrote:
> Done: git://github.com/cconstantine/clojure.contrib.git
>
> Please feel free to be brutal on the code review. The last thing I
> want is for clojure to get dirtied up with bad code.
Just a minor nit -
Shouldn't the function ``creating-timing-map'' be called
``create-timing-map'
How 'bout something like Ruby Gems?
Having to svn and build the clojure-contrib sources is a hassle for some of
us.
On Thu, Apr 16, 2009 at 7:41 AM, Stu Hood wrote:
> I agree. I think the "breaking into modules" approach is the only scalable
> solution.
>
> Someone else mentioned that clojure-co
I agree. I think the "breaking into modules" approach is the only scalable
solution.
Someone else mentioned that clojure-contrib is/shouldbe an incubating area
for core, which seems reasonable. There should be a little more pushback
when a project wants to make it into contrib, and it should alrea
On Apr 15, 2:34 pm, Aaron Feng wrote:
> Hi,
>
> I work for a large financial software company, and we are interested
> in using Clojure for our new project. Due to the concurrent nature of
> the project, we are evaluating three possible languages: Erlang,
> Scala, and Clojure. This project wi
Hi,
I work for a large financial software company, and we are interested
in using Clojure for our new project. Due to the concurrent nature of
the project, we are evaluating three possible languages: Erlang,
Scala, and Clojure. This project will be a hosted solution, but
availability and perfor
On Apr 15, 4:12 pm, Robert Feldt wrote:
> Although I understand each of the concurrency "primitives"/systems
> (stm, agents, atoms, dynvars) in isolation I find it harder to choose
> wisely between them when designing/implementing specific algorithms
> and programs.
>
> Do you have any advice/t
Hi Jim,
Thanks for writing the tutorial!
Kev
On Apr 16, 2:01 am, jim wrote:
> I've just posted a tutorial on using monads in Clojure at
>
> http://intensivesystems.net/tutorials/monads_101.html
>
> It's one big chunk of text since I haven't had time to break it up
> yet. It's also kind of
On Apr 15, 5:07 pm, Stuart Sierra wrote:
> On Apr 15, 2:10 pm, "rzeze...@gmail.com" wrote:
>
> > P.S. I don't want to get off-track, but I also don't understand why
> > ClojureCLR or clojurescript are included in Contrib. I also don't
> > understand why test files are not under their own top
Although I understand each of the concurrency "primitives"/systems
(stm, agents, atoms, dynvars) in isolation I find it harder to choose
wisely between them when designing/implementing specific algorithms
and programs.
Do you have any advice/tips for how to choose between Clojure's
different conc
On Apr 15, 2:10 pm, "rzeze...@gmail.com" wrote:
> P.S. I don't want to get off-track, but I also don't understand why
> ClojureCLR or clojurescript are included in Contrib. I also don't
> understand why test files are not under their own top level dir? I
> think that is a good convention and a
Thanks for all your replies. I was most interested in whether stack
languages provided any easier abstraction capabilities beyond that of
lisp/clojure. I read about the Factor implementation, and about how
continuations, coroutines, and generators were almost trivial to
implement and only required
Dear vimming Clojurians,
a word of warning:
If you have a file containing syntax errors or which contains
a namespace but is not in the Classpath, you probably want
let clj_want_gorilla = 0
in your .vimrc. This also applies if you use files which have
side-effects when they are loaded.
The
You work appears to be geared less toward measuring timing, and more
towards putting bounds on memory and time. I like it :)
On Apr 15, 2:52 pm, Jason Wolfe wrote:
> I have some related contributions ... if clojure.contrib.timing is
> created, maybe some of these would be useful too:
>
> http:/
Done: git://github.com/cconstantine/clojure.contrib.git
Please feel free to be brutal on the code review. The last thing I
want is for clojure to get dirtied up with bad code.
Thanks,
Chris
On Apr 15, 10:45 am, Sean Devlin wrote:
> Start by putting your code on github or something similar :)
I have some related contributions ... if clojure.contrib.timing is
created, maybe some of these would be useful too:
http://groups.google.com/group/clojure/browse_frm/thread/231cc06b4b13744c?hl=en#
-Jason
--~--~-~--~~~---~--~~
You received this message because y
My .02 cents...
I always viewed Contrib as an incubator of sorts for Core. That it
was simply a testing ground for functionality that *MIGHT* make it
into Core if enough people find it useful, or Rich hands down his good
graces.
Requiring a few external libs here and there, and breaking Contrib
> On another note, "closure" is misspelled. If intentional, it should be more
> like "clothure" since it is Lisp. :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send ema
My .02 cents...
I always viewed Contrib as an incubator of sorts for Core. That it
was simply a testing ground for functionality that *MIGHT* make it
into Core if enough people find it useful, or Rich hands down his good
graces.
Requiring a few external libs here and there, and breaking Contrib
Hi Rich,
Bay Area Clojure User Group
http://www.meetup.com/The-Bay-Area-Clojure-User-Group/
Thanks!
Regards,
Amit Rathore.
On Apr 9, 12:00 pm, Rich Hickey wrote:
> Got a Clojure user group, meetup etc?
>
> Reply to this message and let me know, I'll add them to the Clojure
> site.
>
> Please
Dear vimming Clojurians,
I proudly present release 2.1.0 of VimClojure. It needs Clojure rev >=
1349 and Contrib rev >= 650
New features include:
* improved completion (context sensitive, imported classes, aliases,
static class members)
* goto source (by virtue of revision 1349 of clojure)
I've just posted a tutorial on using monads in Clojure at
http://intensivesystems.net/tutorials/monads_101.html
It's one big chunk of text since I haven't had time to break it up
yet. It's also kind of rough, so if you see any typos, misspellings,
errors, etc., post 'em here. Comments as well.
Sorry the subject of my previous post was not what was in the message
body:
Here is the link to the destructuring binding in def which i find
useful sometimes when debugging a function in repl:
http://clojure101.blogspot.com/2009/04/destructuring-binding-support-in-def.html
On Apr 15, 11:05 am,
i'd like to see a migration process where by contribs that turn out to be
"core" make it to the core. Think about newbies that are used to installing
one thing (a language) and getting quite a bit of obviously useful stuff.
The more central (the more other contribs dependent on it) the higher the
On Mar 17, 11:56 pm, gdscott wrote:
>
> One final note -- start-handling-break resets the break-threads map to
> {} every time it is called, meaning that add-break-thread! effectively
> sets the thread its called on as the *only* thread to have a break.
> Is that a bug?
Yep, thanks for the repor
Recently I had written some codes which my colleagues suggested should
be put in a blog. So i have created a new blog for adding my two cents
to the wonderful world of clojure.
http://clojure101.blogspot.com
--~--~-~--~~~---~--~~
You received this message because
Start by putting your code on github or something similar :)
On Apr 14, 8:01 pm, Chris wrote:
> While playing around with clojure I've found the (time ...) macro
> isn't as powerful as I'd like. To fix this I made a timing library to
> help me figure out where all my runtime is going. If other
Check out the thread below in the Compojure group. Specifically, look
for the comment by Brain Carper
http://groups.google.com/group/compojure/browse_thread/thread/67d92ceb4128a375?hl=en
Brian's code:
http://briancarper.net/clojure/compojure-doc.clj
This might be an alternate approach to the
On Apr 15, 2009, at 14:28, Meikel Brandmeyer wrote:
>> As an example, take algebraic data types as defined in
>> clojure.contrib.types. A simple binary tree structure can be defined
>> with
>>
>> (defadt ::tree
>> empty-tree
>> (leaf value)
>> (node left-tree right-tree))
>>
>> Values of th
Hi,
Am 15.04.2009 um 14:04 schrieb Konrad Hinsen:
As an example, take algebraic data types as defined in
clojure.contrib.types. A simple binary tree structure can be defined
with
(defadt ::tree
empty-tree
(leaf value)
(node left-tree right-tree))
Values of this type are represented as m
Hi,
Am 15.04.2009 um 11:37 schrieb Sigrid:
I'm just starting with clojure and want to use vimclojure for
development. I have an error on startup that has been discussed here
in March:
Error detected while processing function
vimclojure#ExecuteNailWithInput:
line 23:
E605: Exception not caugh
On Apr 15, 2009, at 13:31, Rich Hickey wrote:
> That's an open question. There are many reasons it is better as a
> normal key. The arguments for being metadata are:
>
> It allows for things other than maps to have 'types'
> It doesn't impact equality
> It doesn't appear as a 'field' to other cod
On Apr 14, 11:11 am, Stuart Sierra
wrote:
> On Apr 13, 9:12 pm, Rich Hickey wrote:
>
> > :tagis applied to source forms to communicatetypehints to the
> > compiler. :typecan be used, by convention, to add 'typenames' to
> > runtime data structures that support metadata. Thetypefunction will
>
Hi,
I'm just starting with clojure and want to use vimclojure for
development. I have an error on startup that has been discussed here
in March:
Error detected while processing function
vimclojure#ExecuteNailWithInput:
line 23:
E605: Exception not caught: Couldn't execute Nail! Users/hunli/.vi
Hi,
I'm just starting with clojure and want to use vimclojure for
development. I have an error on startup that has been discussed here
in March:
Error detected while processing function
vimclojure#ExecuteNailWithInput:
line 23:
E605: Exception not caught: Couldn't execute Nail! Users/hunli/.vi
While playing around with clojure I've found the (time ...) macro
isn't as powerful as I'd like. To fix this I made a timing library to
help me figure out where all my runtime is going. If other people
find it useful I'd like to get it into contrib.
Simple overview of clojure.contrib.timing:
c
+1 I said the same thing on IRC
On Apr 14, 11:27 am, Mark Reid wrote:
> Hi,
>
> I'm not sure if this is relevant to this discussion but, as a
> newcomer, I was puzzled by the organisation of the clojure-contrib
> source.
>
> Why, for example, are ClojureCLR and clojurescript at the top of the
>
37 matches
Mail list logo
