Hi,
Am 13.12.2010 um 23:52 schrieb Ken Wesson:
> That's not what I meant. I figure all of us have tabs permanently open
> to there (I have two actually). What we don't have is the whole thing
> memorized, or the time to read it all rather than use it for reference […]
My solution to this problem
Hi,
Am 14.12.2010 um 04:25 schrieb Sunil S Nandihalli:
> yeah cool I can do that.. thx. But I remember seeing a syntax for it in the
> ns macro...
(ns name.space
(:refer-clojure :rename {+ core+}))
Please note that / is a special case symbol. Slashes are not allowed in
symbols, and I'm not
On 14 December 2010 09:22, Meikel Brandmeyer wrote:
>
> Am 13.12.2010 um 23:52 schrieb Ken Wesson:
>
>> That's not what I meant. I figure all of us have tabs permanently open
>> to there (I have two actually). What we don't have is the whole thing
>> memorized, or the time to read it all rather th
On Tue, Dec 14, 2010 at 4:52 AM, James Reeves wrote:
> On 14 December 2010 09:22, Meikel Brandmeyer wrote:
>>
>> Am 13.12.2010 um 23:52 schrieb Ken Wesson:
>>
>>> That's not what I meant. I figure all of us have tabs permanently open
>>> to there (I have two actually). What we don't have is the w
javajosh writes:
> Ok, I decided to nuke ports, fink, and delete every package they ever
> installed. I successfully installed emacs 23.2 via homebrew (there's a
> good overview of homebrew here
> http://ascarter.net/2010/02/22/homebrew-for-os-x.html).
I'm coming late to this game, and I see tha
There has been much thought lately around build and release processes.
See http://dev.clojure.org/display/design/Common+Contrib+Build
The goal is to to have more libraries under the umbrella of "contrib"
without requiring them to keep to the same release schedule. Each library
can have its own
Howdy,
I asked this on #clojure and posted a question on Stackoverflow
(http://stackoverflow.com/questions/4424220/how-do-i-rebind-a-var-in-a-
lazytest-describe-test), but no dice. I'm assuming that it's because
this is so simple and I'm doing it so incorrectly that nobody can even
begin to formu
I am currently working on an MPI package for Clojure.
This crossed my mailbox and may be of interest to the
clojure community.
Tim Daly
~~
4th European Lisp Symposium
Special Focus on Parall
Any reason why the doc string has been removed from clojure.xml/emit
(and emit-element)? Are these functions deprecated?
--
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
On Dec 14, 2010, at 18:00 , Ralph wrote:
> Any reason why the doc string has been removed from clojure.xml/emit
> (and emit-element)? Are these functions deprecated?
>
Well, they're buggy.
http://www.assembla.com/spaces/clojure/search?q=clojure.xml+emit
On issue 412 Stuart Halloway explains:
Not to sound like a one track record here, but you should look at
clojure.contrib.generic.arithemetic to see how to redefine /
have a great day,
--Robert McIntyre
On Tue, Dec 14, 2010 at 4:26 AM, Meikel Brandmeyer wrote:
> Hi,
>
> Am 14.12.2010 um 04:25 schrieb Sunil S Nandihalli:
>
>> yeah coo
Both `describe` and `it` create functions. That is, they expand out
to `(fn [] ...)`. Wrapping `binding` around the creation of a fn has
no effect.
For finer control over where the fn gets created and how failures get
reported, you can use `do-it` and `expect`.
(describe ...
(do-it ...
(b
Hi,
Am 14.12.2010 um 19:04 schrieb Robert McIntyre:
> Not to sound like a one track record here, but you should look at
> clojure.contrib.generic.arithemetic to see how to redefine /
Which does not make / a legal symbol. Slashes are not allowed in Symbols and
the future of this code is not guar
On Dec 14, 2:31 am, Konrad Hinsen wrote:
> That's actually what clojure.contrib.complex-numbers already uses! And
> it's based on multimethods, not protocols, because of all those binary
> operations.
It is possible, though not trivial, to do 2-argument dispatch with
protocols. See http://pa
I wouldn't worry too much about your reputation. Your posts are top
notch, and you obviously know the language better than 90% of most
clojure users. Have confidence and laugh if you think someone is
disparaging: actions speak far louder than words.
On Dec 14, 4:42 am, Ken Wesson wrote:
> On Tu
On Tue, Dec 14, 2010 at 2:23 PM, javajosh wrote:
> I wouldn't worry too much about your reputation. Your posts are top
> notch, and you obviously know the language better than 90% of most
> clojure users.
Thank you.
> Have confidence and laugh if you think someone is
> disparaging: actions speak
Hi all,
My apologies for resurrecting a dead thread of discussion if this has
already been put to bed, but I was wondering if anyone has been working
on implementing a bit syntax for Clojure in the rough conceptual style
of Erlang's bit syntax.
I say conceptual because I'm not necessarily looking
On Tue, Dec 14, 2010 at 8:02 AM, Stuart Sierra
wrote:
> There has been much thought lately around build and release processes.
> See http://dev.clojure.org/display/design/Common+Contrib+Build
Thanx.
> The goal is to to have more libraries under the umbrella of "contrib"
> without requiring them
For now, you can just look at the repository
at http://build.clojure.org/releases/org/clojure/
Once we get automated releases from Hudson/Maven (real soon now) the JARs
will be deployed to the Maven Central repository, where they will be
automatically indexed by search engines like jarvana.com.
(defn fact [n] (reduce * (range 1 (inc n
(fact 100)
This produces the right result on 1.2 but "ArithmeticException integer
overflow" on 1.3-alpha4.
Is this intentional?
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send
On Dec 14, 6:30 pm, Miki wrote:
> (defn fact [n] (reduce * (range 1 (inc n
> (fact 100)
>
> This produces the right result on 1.2 but "ArithmeticException integer
> overflow" on 1.3-alpha4.
> Is this intentional?
Primitive math is the default in 1.3
--
You received this message because you a
Hi guys,
I love to listen to mp3's that I've downloaded, on my way to work. I think
it would be great to compile a list of links to Clojure-based mp3's. I love
InfoQ, but not all of the videos are downloadable.
Here are my first two:
Stuart Halloway on "Clojure and Functional Programming"
http
As Brian said, primitive math is now the default in 1.3. If auto-
promotion on overflow is desired, you can use the +', -', *', inc',
dec' functions (note the single quote suffix).
http://dev.clojure.org/display/doc/Enhanced+Primitive+Support
On Dec 14, 5:36 pm, Brian Goslinga wrote:
> On Dec 1
Of course, TANSTAAFL: the auto-promoting version of the functions will
be slower than their primitive counterparts.
On Dec 14, 6:23 pm, Benny Tsai wrote:
> As Brian said, primitive math is now the default in 1.3. If auto-
> promotion on overflow is desired, you can use the +', -', *', inc',
> de
On Tue, Dec 14, 2010 at 8:23 PM, Benny Tsai wrote:
> As Brian said, primitive math is now the default in 1.3. If auto-
> promotion on overflow is desired, you can use the +', -', *', inc',
> dec' functions (note the single quote suffix).
Why was this done? I preferred having +, -, etc. DTRT in g
On Tue, Dec 14, 2010 at 9:04 PM, Ken Wesson wrote:
> On Tue, Dec 14, 2010 at 8:23 PM, Benny Tsai wrote:
> > As Brian said, primitive math is now the default in 1.3. If auto-
> > promotion on overflow is desired, you can use the +', -', *', inc',
> > dec' functions (note the single quote suffix)
On Dec 14, 8:04 pm, Ken Wesson wrote:
> On Tue, Dec 14, 2010 at 8:23 PM, Benny Tsai wrote:
> > As Brian said, primitive math is now the default in 1.3. If auto-
> > promotion on overflow is desired, you can use the +', -', *', inc',
> > dec' functions (note the single quote suffix).
>
> Why was
On Tue, Dec 14, 2010 at 9:56 PM, David Nolen wrote:
> On Tue, Dec 14, 2010 at 9:04 PM, Ken Wesson wrote:
>>
>> On Tue, Dec 14, 2010 at 8:23 PM, Benny Tsai wrote:
>> > As Brian said, primitive math is now the default in 1.3. If auto-
>> > promotion on overflow is desired, you can use the +', -',
On Tue, Dec 14, 2010 at 10:02 PM, Brian Goslinga
wrote:
> This topic has been discussed to death before on this group.
If so, it was before I joined.
> Doing the right thing is actually harder than you might first think
But it's also already being done by Clojure 1.2 so I don't see how
that's r
On Dec 14, 2010, at 9:26 PM, Ken Wesson wrote:
> On Tue, Dec 14, 2010 at 10:02 PM, Brian Goslinga
> wrote:
>> This topic has been discussed to death before on this group.
>
> If so, it was before I joined.
That's what archives are for:
http://groups.google.com/group/clojure/search?group=clojur
Just ran across:
http://steve-yegge.blogspot.com/2006/04/lisp-is-not-acceptable-lisp.html
Whoah! I had no idea there was so much, uh, 'intricacy' going on
behind Lisp. :)
Anyway, it was interesting to read it having a bit of Clojure under my
belt. With the exception of types, it seems like Clo
On Dec 14, 9:24 pm, Ken Wesson wrote:
> Breaking source compatibility with just about every single preexisting
> line of Clojure code out there is supposed to make our lives *easier*?
Actually, it appears that the majority of the lines of code out there
use integers that fit inside a long, so the
javajosh writes:
> Just ran across:
>
> http://steve-yegge.blogspot.com/2006/04/lisp-is-not-acceptable-lisp.html
>
> Whoah! I had no idea there was so much, uh, 'intricacy' going on
> behind Lisp. :)
>
> Anyway, it was interesting to read it having a bit of Clojure under my
> belt. With the exc
On Tue, Dec 14, 2010 at 6:04 PM, Ken Wesson wrote:
> On Tue, Dec 14, 2010 at 8:23 PM, Benny Tsai wrote:
> > As Brian said, primitive math is now the default in 1.3. If auto-
> > promotion on overflow is desired, you can use the +', -', *', inc',
> > dec' functions (note the single quote suffix)
Steve is trolling with that Lisp post.
There is so much noise in what he says,
there is no point beginning to reply.
And all of it would be off-topic.
Ignore it.
Tim Daly
On 12/14/2010 11:23 PM, Alex Osborne wrote:
javajosh writes:
Just ran across:
http://steve-yegge.blogspot.com/2006/0
On Tue, Dec 14, 2010 at 7:02 PM, Brian Goslinga wrote:
> (Since java.lang.BigInteger is
> slow on small numbers, clojure.lang.BigInt is also being introduced
> (which is the type of 1N) that should be as fast as math was in 1.2
> when the numbers fit into a long)
>
AFAIK, this hasn't been done y
The functions get-in, assoc-in, update-in are really useful. Just
wanted to share a thoughts.
user=> (def m {:a {:b {:c 10 :c1 20} :b1 90} :a1 100})
#'user/m
1. Lets see the behavior of these functions in the corner case of
empty keyseq:
user=> (get-in m [])
{:a {:b {:c 10, :c1 20}, :b1 90}, :a1
I'm using IntelliJ Idea 10 with the La Closure plugin version 0.3.15
and Java 6 I've added Clojure 1.2 to a project.
The breakpoints I put on Java code get hit, but the ones I put on
Clojure do not. in fact, if the debugger is stopped on a Java
breakpoint, the breakpoints on Clojure code have a
One thing I've argued for in the past, but got no traction:
We have:
get-in, get
assoc-in, assoc
update-in, ?
Let's add update to go with update-in.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegro
On Wed, Dec 15, 2010 at 12:12 AM, Mark Engelberg
wrote:
> One thing I've argued for in the past, but got no traction:
> We have:
> get-in, get
> assoc-in, assoc
> update-in, ?
> Let's add update to go with update-in.
Let's give them absolutely no excuse like "we don't have time to write
the code
On Tue, Dec 14, 2010 at 10:37 PM, Michael Gardner wrote:
> On Dec 14, 2010, at 9:26 PM, Ken Wesson wrote:
>
>> On Tue, Dec 14, 2010 at 10:02 PM, Brian Goslinga
>> wrote:
>>> This topic has been discussed to death before on this group.
>>
>> If so, it was before I joined.
>
> That's what archives
On Tue, Dec 14, 2010 at 10:57 PM, Brian Goslinga
wrote:
> On Dec 14, 9:24 pm, Ken Wesson wrote:
>> Breaking source compatibility with just about every single preexisting
>> line of Clojure code out there is supposed to make our lives *easier*?
> Actually, it appears that the majority of the lines
On Wed, Dec 15, 2010 at 12:22 AM, Ken Wesson wrote:
>
> Are you honestly suggesting I search the archives for every word of
> every thought that it ever occurs to me to post here?
>
With all due respect, the topic has already been bike shedded into the
ground by many members in the community. Wh
My main question is, what tasks/apps is clojure ideally suited for?
I've been playing with implementing Binary Search Trees in clojure and
Java as a way to learn clojure and compare the two languages. My
original thought was to implement some basic data types and algorithms
in a handful of int
On Wed, Dec 15, 2010 at 12:38 AM, David Nolen wrote:
> On Wed, Dec 15, 2010 at 12:22 AM, Ken Wesson wrote:
>>
>> Are you honestly suggesting I search the archives for every word of
>> every thought that it ever occurs to me to post here?
>
> With all due respect, the topic has already been bike s
On Wed, Dec 15, 2010 at 12:49 AM, Todd wrote:
> My main question is, what tasks/apps is clojure ideally suited for?
>
> I've been playing with implementing Binary Search Trees in clojure and Java
> as a way to learn clojure and compare the two languages. My original thought
> was to implement some
On Wed, Dec 15, 2010 at 12:50 AM, Ken Wesson wrote:
> On Wed, Dec 15, 2010 at 12:38 AM, David Nolen
> wrote:
> > On Wed, Dec 15, 2010 at 12:22 AM, Ken Wesson wrote:
> >>
> >> Are you honestly suggesting I search the archives for every word of
> >> every thought that it ever occurs to me to post
Clojure's getting better all the time at implementing Java-like things
without dropping down to Java. But the whole point of programming Clojure
is to be "more functional", using and creating persistent data structures
that work well with its STM. Coding an imperative, mutable BST in Clojure
isn
On Dec 14, 2010, at 11:22 PM, Ken Wesson wrote:
> On Tue, Dec 14, 2010 at 10:37 PM, Michael Gardner wrote:
>> That's what archives are for
>
> Are you honestly suggesting I search the archives for every word of
> every thought that it ever occurs to me to post here?
>
> I don't have that kind o
On Tue, Dec 14, 2010 at 10:08 PM, Mark Engelberg
wrote:
> Coding an imperative, mutable BST in Clojure isn't going to be its strong
> suit.
>
>
Maybe you didn't do this though. I didn't read your code carefully. I just
saw the "delete" in your protocol and assumed it was mutable.
--
You recei
On Wed, Dec 15, 2010 at 1:08 AM, Mark Engelberg wrote:
> Clojure's getting better all the time at implementing Java-like things
> without dropping down to Java. But the whole point of programming Clojure
> is to be "more functional", using and creating persistent data structures
> that work well
you may want to also post this on the jetbrains la clojure forum
http://devnet.jetbrains.net/community/idea/clojure?view=discussions
On Wed, Dec 15, 2010 at 12:00 AM, HiHeelHottie wrote:
>
> I'm using IntelliJ Idea 10 with the La Closure plugin version 0.3.15
> and Java 6 I've added Clojure 1.2
On Dec 14, 8:52 pm, ka wrote:
> user=> (get-in m [])
> {:a {:b {:c 10, :c1 20}, :b1 90}, :a1 100}
This seems strange to me. I would expect Clojure to return nil, as
there is no key in there that is nil. Assuming that an empty vector is
the same as asking for a nil key, that is.
(I suppose it ma
On Dec 15, 6:12 am, Mark Engelberg wrote:
> One thing I've argued for in the past, but got no traction:
> We have:
> get-in, get
> assoc-in, assoc
> update-in, ?
> Let's add update to go with update-in.
update should really be in there. I always try to write update then i
remember that I have to
Lisp is Not an Acceptable Lisp
Friday, April 14, 2006
Clojure wasn't out then.
--
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 - please be pa
55 matches
Mail list logo
