I love you all !!!
--
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 patient with your
first post.
To unsubscribe from this group,
Updated.
On Sep 5, 3:30 pm, Andy Fingerhut wrote:
> I've created a modified version of the cheatsheet, including PDF files with
> clickable links, here:
>
> http://homepage.mac.com/jafingerhut/files/cheatsheet-2.0.html
>
> There is a list of changes made, including the one you mention, Stuart, an
That's a cool link and an interesting read! Thanks, Stefan!
Dominikus
On Sep 5, 10:23 pm, Stefan Kamphausen wrote:
> Hi,
>
> there is another paper in the wild which very nicely describes, how
> Clojure's implementation of STM works and how it compares to other
> management strategies for resolv
I've created a modified version of the cheatsheet, including PDF files with
clickable links, here:
http://homepage.mac.com/jafingerhut/files/cheatsheet-2.0.html
There is a list of changes made, including the one you mention, Stuart, and
some others regarding transients that had been suggested a w
Hi Chris,
could you please elaborate a bit on the swank-clojure issue? Alternatively
just point me to the threads that I should have read more closely.
Thanks and kind regards,
Stefan
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this
Hi,
there is another paper in the wild which very nicely describes, how
Clojure's implementation of STM works and how it compares to other
management strategies for resolving conflicts.
http://vbn.aau.dk/files/32587755/report.pdf
Definitely worth a read, I think.
Best,
Stefan
--
You receiv
FWIW I've had to re-remember this behavior of "contains?" several times, and to
warn students off of it because it's so easy to think from the name that it's a
general membership test. And the "some" idiom takes a while to remember.
The cheat sheet may indeed be contributing to the problem -- I
Yes, release notes are in progress here:
http://dev.clojure.org/display/doc/1.3
Stuart Sierra
clojure.com
--
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
Hi Sam,
Namespace names and Var names live in separate, er, namespaces, so they're
allowed to overlap. A bare symbol will never resolve to a Namespace object,
you have to call `the-ns` to get the Namespace. But it's confusing to have
overlapping names, so I would recommend avoiding it.
-Stua
Hi folks, just looking at the Clojure Cheat Sheet
http://clojure.org/cheatsheet
The `contains?` function is under "Collections -> Collections -> Content
tests." That implies that it's testing the values of the collection, which
it doesn't exactly do, a frequent source of confusion.
My suggesti
My CA has been mailed yesterday, should be in by Friday.
I'll post my registration request to clojure-dev around that time.
I'll have a look at the issue this week.
Luc
On Sun, 4 Sep 2011 14:10:17 -0700 (PDT)
Stuart Sierra wrote:
> FYI, I spoke with Luc and told him I'm happy to have c.c.trace
On Sep 5, 8:46 am, Terje Dahl wrote:
> Ref: Stuart Halloway's talk: "Simplicity":
>
> http://blip.tv/clojure/stuart-halloway-simplicity-ain-t-easy-4842694
>
> Found via reading list:http://clojure.com/reading.html)
>
> At one point in his talk he states that defrecord is in fact basically
> "docu
2011/9/5 Mark Rathwell
> >> Huh, interesting. I assumed ^:foo meta syntax was new to 1.3, and
> >> wouldn't compile at all in 1.2. But now I see that in 1.2 it's
> >> equivalent to ^{:tag :foo} - not useful, but not damaging either. I
> >> guess I'll start using ^:dynamic myself.
> >
> > Actually
Ref: Stuart Halloway's talk: "Simplicity":
http://blip.tv/clojure/stuart-halloway-simplicity-ain-t-easy-4842694
Found via reading list: http://clojure.com/reading.html )
At one point in his talk he states that defrecord is in fact basically
"documented, named [typed] structure".
(as opposed to
Hi there,
The docstring for one of the Overtone ugens fns isn't printing correctly - it's
returning an empty docstring. I discovered that that particular ugen has the
same name as one of the namespaces that is visible at that scope. The fn is
called osc and the namespace for sending and receivi
>> Huh, interesting. I assumed ^:foo meta syntax was new to 1.3, and
>> wouldn't compile at all in 1.2. But now I see that in 1.2 it's
>> equivalent to ^{:tag :foo} - not useful, but not damaging either. I
>> guess I'll start using ^:dynamic myself.
>
> Actually, it causes compiler errors, when the
2011/9/5 Dominikus
> Right, it's "according to the spec", but it doesn't explain the
> behavior. as I noticed this morning http://clojure.org/refs references
> http://en.wikipedia.org/wiki/Multiversion_concurrency_control (the
> technique used to implement STM) which provides an explanation for t
Woops. And indeed I'm wrong. It was {:type ::my-type}, not {:tag ::my-type}.
Nevermind.
So ^ now distinguishes between keywords and classes, which it didn't before.
Sorry for the noise.
Am Sonntag, 4. September 2011 09:54:20 UTC+2 schrieb Meikel Brandmeyer
(kotarak):
>
> #^something was equiva
2011/9/3 Alan Malloy
> Huh, interesting. I assumed ^:foo meta syntax was new to 1.3, and
> wouldn't compile at all in 1.2. But now I see that in 1.2 it's
> equivalent to ^{:tag :foo} - not useful, but not damaging either. I
> guess I'll start using ^:dynamic myself.
>
Actually, it causes compile
Right, it's "according to the spec", but it doesn't explain the
behavior. as I noticed this morning http://clojure.org/refs references
http://en.wikipedia.org/wiki/Multiversion_concurrency_control (the
technique used to implement STM) which provides an explanation for the
experienced behavior:
If
2011/9/5 Meikel Brandmeyer (kotarak)
> Salut Laurent,
>
Hallo Meikel,
>
> Am Sonntag, 4. September 2011 21:51:20 UTC+2 schrieb lpetit:
>
>> Interesting!
>>
>> I don't see the link between the README page and the currrent state of the
>> API, though. Is the README ahead of time, or is the desig
Great news!
Is good documentation on new 1.3 features also coming?
--
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 patient with y
22 matches
Mail list logo
