Errata

433 views
Skip to first unread message

Erik Assum

unread,
Mar 17, 2016, 2:52:35 PM3/17/16
to Elements of Clojure
Hi, and thanks for a great book!

There seems to be a formatting error on the :to-soft keyword in bed-errors

Really enjoying this book!

Erik.

Zach Tellman

unread,
Mar 17, 2016, 2:55:57 PM3/17/16
to Erik Assum, Elements of Clojure
So there is.  Fixed, thank you.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elements-of-clojure/30868132-dea8-47da-b5e4-a0c2036b75d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Erik Assum

unread,
Mar 17, 2016, 2:58:44 PM3/17/16
to Elements of Clojure
And a bit further:
"There cannot be hard and fast guidelines for choosing a good name, since they have to judged within their context."

Missing "be"

Zach Tellman

unread,
Mar 17, 2016, 3:01:48 PM3/17/16
to Erik Assum, Elements of Clojure
Also fixed.  Keep them coming.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.

Rick Moynihan

unread,
Mar 17, 2016, 6:23:52 PM3/17/16
to Elements of Clojure
Page 14

"A function which converts to the payload to a Base64 encoding should be called
->base64"

s/to the payload/the payload/

R.




On Thursday, 17 March 2016 19:01:48 UTC, Zach Tellman wrote:
Also fixed.  Keep them coming.

On Thu, Mar 17, 2016 at 11:58 AM Erik Assum <er...@assum.net> wrote:
And a bit further:
"There cannot be hard and fast guidelines for choosing a good name, since they have to judged within their context."

Missing "be"

 17. mars 2016 19.52.35 UTC+1 skrev Erik Assum følgende:
> Hi, and thanks for a great book!
>
> There seems to be a formatting error on the :to-soft keyword in bed-errors
>
> Really enjoying this book!
>
> Erik.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clojure+unsub...@googlegroups.com.

Zach Tellman

unread,
Mar 17, 2016, 6:26:55 PM3/17/16
to Rick Moynihan, Elements of Clojure
Fixed, thanks.

On Thu, Mar 17, 2016 at 3:23 PM Rick Moynihan <rick.m...@gmail.com> wrote:
Page 14

"A function which converts to the payload to a Base64 encoding should be called
->base64"

s/to the payload/the payload/

R.




On Thursday, 17 March 2016 19:01:48 UTC, Zach Tellman wrote:
Also fixed.  Keep them coming.

On Thu, Mar 17, 2016 at 11:58 AM Erik Assum <er...@assum.net> wrote:
And a bit further:
"There cannot be hard and fast guidelines for choosing a good name, since they have to judged within their context."

Missing "be"

 17. mars 2016 19.52.35 UTC+1 skrev Erik Assum følgende:
> Hi, and thanks for a great book!
>
> There seems to be a formatting error on the :to-soft keyword in bed-errors
>
> Really enjoying this book!
>
> Erik.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.

To post to this group, send email to elements-...@googlegroups.com.

Tom Coupland

unread,
Mar 18, 2016, 11:54:30 AM3/18/16
to Elements of Clojure, rick.m...@gmail.com
End of page 9: "When defining a let-bound value, we also only control the sign, but we also control the right side of the let binding"

That also should be 'not' I think.

Erik Assum

unread,
Mar 18, 2016, 4:49:01 PM3/18/16
to Elements of Clojure

 
Erik. 

Zach Tellman

unread,
Mar 18, 2016, 5:10:32 PM3/18/16
to Erik Assum, Elements of Clojure
I'm hosting ideolalia.com, aleph.io, and elementsofclojure.com on the same server, and my "Host" header detection logic was a little too simplistic.  Fixed now, thanks.

On Fri, Mar 18, 2016 at 1:49 PM Erik Assum <er...@assum.net> wrote:

 
Erik. 

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.

Ed Phillips

unread,
Mar 20, 2016, 1:54:26 PM3/20/16
to Elements of Clojure
Hello,

Thanks for such fine writing and thinking. I'm impressed, amongst much else in your first chapter, by your apposite use of Frege and friends.

I note one erratum on page 14, in the first paragraph:

"The naming convention given here" should be modified to the plural "The naming conventions given here".

Zach Tellman

unread,
Mar 20, 2016, 5:20:16 PM3/20/16
to Ed Phillips, Elements of Clojure
Fixed, thank you.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.

Tim Jones

unread,
Mar 22, 2016, 5:35:42 PM3/22/16
to Elements of Clojure, edwar...@gmail.com
Middle of page 5: ".. both names are share a reference, .. " -> maybe "both names share a reference".

On Sunday, March 20, 2016 at 2:20:16 PM UTC-7, Zach Tellman wrote:
Fixed, thank you.

On Sun, Mar 20, 2016 at 10:54 AM Ed Phillips <edwar...@gmail.com> wrote:
Hello,

Thanks for such fine writing and thinking. I'm impressed, amongst much else in your first chapter, by your apposite use of Frege and friends.

I note one erratum on page 14, in the first paragraph:

"The naming convention given here" should be modified to the plural "The naming conventions given here".





On Thursday, March 17, 2016 at 11:52:35 AM UTC-7, Erik Assum wrote:
Hi, and thanks for a great book!

There seems to be a formatting error on the :to-soft keyword in bed-errors

Really enjoying this book!

Erik.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clojure+unsub...@googlegroups.com.

Zach Tellman

unread,
Mar 22, 2016, 5:38:00 PM3/22/16
to Tim Jones, Elements of Clojure, edwar...@gmail.com
Fixed, thanks.

On Tue, Mar 22, 2016 at 2:35 PM Tim Jones <timofe...@gmail.com> wrote:
Middle of page 5: ".. both names are share a reference, .. " -> maybe "both names share a reference".

On Sunday, March 20, 2016 at 2:20:16 PM UTC-7, Zach Tellman wrote:
Fixed, thank you.

On Sun, Mar 20, 2016 at 10:54 AM Ed Phillips <edwar...@gmail.com> wrote:
Hello,

Thanks for such fine writing and thinking. I'm impressed, amongst much else in your first chapter, by your apposite use of Frege and friends.

I note one erratum on page 14, in the first paragraph:

"The naming convention given here" should be modified to the plural "The naming conventions given here".





On Thursday, March 17, 2016 at 11:52:35 AM UTC-7, Erik Assum wrote:
Hi, and thanks for a great book!

There seems to be a formatting error on the :to-soft keyword in bed-errors

Really enjoying this book!

Erik.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.

To post to this group, send email to elements-...@googlegroups.com.

Matt Taylor

unread,
Mar 25, 2016, 3:22:53 AM3/25/16
to Elements of Clojure
Page 18

"However, some macros are too complex to be understand through their macroexpanded form."

s/understand/understood/

Matt

Zach Tellman

unread,
Mar 28, 2016, 1:26:13 PM3/28/16
to Matt Taylor, Elements of Clojure
Thanks, fixed.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.

jjttjj

unread,
Apr 15, 2016, 3:17:05 PM4/15/16
to Elements of Clojure
Page 25:
"In this case, if numbers has zero arguments in it"

Arguments should be "elements"

Erik Assum

unread,
Jul 23, 2016, 3:39:11 PM7/23/16
to Elements of Clojure
Thanks for the new installment, I've been waiting:)

In the "binding" chapter, you have the following:

«(defn b [x turbo-mode?]
(c x))»

I do believe you forgot to pass along turbo-mode?

Erik.

Zach Tellman

unread,
Jul 23, 2016, 4:14:04 PM7/23/16
to Erik Assum, Elements of Clojure
Yeah, I did.  Thanks, I'll publish a fix.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.

Shaun Parker

unread,
Sep 2, 2016, 2:52:55 PM9/2/16
to Elements of Clojure
On page 30 of the July 26th PDF:
 
This is especially true for the top-level configurations for an application; the the parameters are provided at the entry point for the process, and have to propagate into many different parts of the code.


Zach Tellman

unread,
Sep 3, 2016, 10:38:34 PM9/3/16
to Shaun Parker, Elements of Clojure
Thanks, this will be fixed in the next release.

On Fri, Sep 2, 2016 at 11:52 AM Shaun Parker <sh...@lohilabs.com> wrote:
On page 30 of the July 26th PDF:
 
This is especially true for the top-level configurations for an application; the the parameters are provided at the entry point for the process, and have to propagate into many different parts of the code.


--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.

James Elliott

unread,
Feb 23, 2017, 12:52:24 PM2/23/17
to Elements of Clojure, sh...@lohilabs.com
Thanks for continuing to write such a meaningful, thought-provoking guide! There’s a small typo in the lower half of PDF page 57 in version 
a43e7fec8d9030031e03e2d0e2d23c838766e4a4 released on February 12, 2017:We can possess a oracles, but we can never understand them. should not have the “a” in it.

James Elliott

unread,
Feb 23, 2017, 2:28:32 PM2/23/17
to Elements of Clojure, sh...@lohilabs.com
In the same version, near the top of PDF page 61, “A useful abstraction should also be adaptable; it must allow be able to change with its environment.” seems to have an extra “allow” in it as well.

Zach Tellman

unread,
Feb 23, 2017, 2:45:23 PM2/23/17
to James Elliott, Elements of Clojure, sh...@lohilabs.com
Thanks James, those will both be fixed in the next release.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.

Thomas Schranz

unread,
Aug 29, 2017, 8:53:04 PM8/29/17
to Elements of Clojure, ja...@brunchboy.com, sh...@lohilabs.com
I might already be too tired but it seems like on page 59 the function body should read (b x turbo-mode?) but is missing the question mark.


On Thursday, February 23, 2017 at 8:45:23 PM UTC+1, Zach Tellman wrote:
Thanks James, those will both be fixed in the next release.

On Thu, Feb 23, 2017 at 11:28 AM James Elliott <ja...@brunchboy.com> wrote:
In the same version, near the top of PDF page 61, “A useful abstraction should also be adaptable; it must allow be able to change with its environment.” seems to have an extra “allow” in it as well.


On Thursday, February 23, 2017 at 11:52:24 AM UTC-6, James Elliott wrote:
Thanks for continuing to write such a meaningful, thought-provoking guide! There’s a small typo in the lower half of PDF page 57 in version 
a43e7fec8d9030031e03e2d0e2d23c838766e4a4 released on February 12, 2017:We can possess a oracles, but we can never understand them. should not have the “a” in it.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clojure+unsub...@googlegroups.com.

Zach Tellman

unread,
Aug 30, 2017, 1:19:03 AM8/30/17
to Thomas Schranz, Elements of Clojure, ja...@brunchboy.com, sh...@lohilabs.com
That's correct, thanks for catching that.

On Wed, Aug 30, 2017 at 2:53 AM Thomas Schranz <tho...@blossom.io> wrote:
I might already be too tired but it seems like on page 59 the function body should read (b x turbo-mode?) but is missing the question mark.


On Thursday, February 23, 2017 at 8:45:23 PM UTC+1, Zach Tellman wrote:
Thanks James, those will both be fixed in the next release.

On Thu, Feb 23, 2017 at 11:28 AM James Elliott <ja...@brunchboy.com> wrote:
In the same version, near the top of PDF page 61, “A useful abstraction should also be adaptable; it must allow be able to change with its environment.” seems to have an extra “allow” in it as well.


On Thursday, February 23, 2017 at 11:52:24 AM UTC-6, James Elliott wrote:
Thanks for continuing to write such a meaningful, thought-provoking guide! There’s a small typo in the lower half of PDF page 57 in version 
a43e7fec8d9030031e03e2d0e2d23c838766e4a4 released on February 12, 2017:We can possess a oracles, but we can never understand them. should not have the “a” in it.

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.

To post to this group, send email to elements-...@googlegroups.com.

Manuel Uberti

unread,
Sep 28, 2017, 9:28:18 AM9/28/17
to Elements of Clojure
Hi,

first of all thanks for all the work on this book. This is my first post here, so please tell me if I am doing something wrong.

I don't know if it's been already pointed out, but at page 80 of the latest release of the book there is an error: 

It’s easy to to imagine a failure of the former assumption;

The second to is not necessary.


Manuel

Manuel Uberti

unread,
Sep 28, 2017, 9:34:31 AM9/28/17
to Elements of Clojure
Another one just spotted, but this could be just my random opinion. Page 82:

Instead, the C++ relies on a convention, known as “resource allocation is initialization” (RAII)

Is the before C++ necessary? Unless there is some word missing after it, it can be left out I guess.


Manuel

Manuel Uberti

unread,
Sep 28, 2017, 9:56:54 AM9/28/17
to Elements of Clojure
Some other ones, I grouped them all in one mail:

Page 83:
 
This clearly a bad assumption; for any given model, small facets of the environment are critically important, and the rest are not

I think there is a missing is there.


Page 84:

This true for software, architecture, biology, urban planning, and a host of other fields.

A missing is here too.


Page 88:

Even so, we are constantly drawn to software we don’t know well enough to dislike.

It could be my poor English, but wouldn't this be better rephrased? Something like: Even so, we are constantly drawn to dislike software we don’t know well enough.


Manuel

Zach Tellman

unread,
Sep 28, 2017, 1:46:58 PM9/28/17
to Manuel Uberti, Elements of Clojure
Thank you for pointing out all the typos. If anyone's wondering, I will be hiring a copy editor before releasing my final draft, but in the meantime I greatly appreciate everyone's help.

As for the last sentence, the intended meaning is the inverse of what you wrote.  I'm saying we are drawn to software we don't know, because we haven't learned all the things that are wrong with it.  I'll think about ways to make the phrasing more clear.

Zach

--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.

Ed Phillips

unread,
Sep 28, 2017, 2:32:59 PM9/28/17
to Zach Tellman, Manuel Uberti, Elements of Clojure
Is there a download available of the entire book for errata readers? I should purchase a copy!

To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clojure+unsub...@googlegroups.com.
To post to this group, send email to elements-of-clojure@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Elements of Clojure" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elements-of-clojure/9vS82jApebs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elements-of-clojure+unsub...@googlegroups.com.
To post to this group, send email to elements-of-clojure@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elements-of-clojure/CADj9HBz6QHEM8u%3Dm-cKMSdcB7-vD5cw-nT-xbQE2T9vX4DcAZg%40mail.gmail.com.

Zach Tellman

unread,
Sep 28, 2017, 3:09:18 PM9/28/17
to Ed Phillips, Manuel Uberti, Elements of Clojure
The book can be purchased at https://leanpub.com/elementsofclojure/.  I'm happy to offer a 50% discount since you've already found a typo in the sample chapter, email me directly if you'd like to take advantage of that.

To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Elements of Clojure" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elements-of-clojure/9vS82jApebs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elements-of-clo...@googlegroups.com.

To post to this group, send email to elements-...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Elements of Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elements-of-clo...@googlegroups.com.
To post to this group, send email to elements-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elements-of-clojure/CALvXzX7WqzGbnLEs6tcWp8qJBmDi1gG1S992yM4YmrqA9Zedaw%40mail.gmail.com.
Message has been deleted

Alex Engelberg

unread,
Mar 27, 2018, 2:45:14 AM3/27/18
to Elements of Clojure
Another erratum for you (from the latest draft):

Page 44, in the third example implementation of the "pi" function: #(pi n) should be #(pi n {}).

Reply all
Reply to author
Forward
0 new messages