Sweet! Thanks for the pointer.
It is a challenge to reverse-engineer someone else's code.
It is even more challenging to understand how it relates
to the algorithm and the idea. This will help a lot.
Tim Daly
On 1/8/2011 6:22 AM, Robert McIntyre wrote:
You may find
http://blog.higher-order.net/2009/02/01/understanding-clojures-persistentvector-implementation/
useful for a clear explanation of PersistentVectors. Maybe even get
in touch with the guy for an addition to the book?
Thanks for your work on a literate clojure.
sincerely,
--Robert McIntyre
On Fri, Jan 7, 2011 at 12:28 AM, Ken Wesson<kwess...@gmail.com> wrote:
On Fri, Jan 7, 2011 at 12:07 AM, Tim Daly<d...@axiom-developer.org> wrote:
Hmmm. I may have misunderstood your point. I thought you were suggesting
writing code that is not part of the distribution in order to get a
minimal running system and then working from that. If that is not what
you're suggesting then I'm confused.
No, I was just suggesting that the order of the material put the stuff
in the distribution that's necessary to bootstrap a minimally
functional repl first, culminating in the eval function and the
command-line repl class, then flesh out the rest of Clojure's
feature-set with the rest of the stuff in the distribution. No new
code.
The pamphlet sources are in a git repository so they are immutable.
Wikis are fine for a lot of things but not for linearizing the
ideas into a readable literate form. Books fulfill that role.
I suggested *maybe* letting the wiki users try to decide,
collectively, on a linearization; maybe that would prove workable and
maybe not. If not, you'd have to linearize it yourself to make the
book version. But if you're looking for section submissons and user
proof-reading a wiki can at least organize that activity, and can
provide "seeds" by having unwritten sections in there with just the
source code that is to be explained. And without potential
contributors maybe being put off by having to learn a whole extra set
of tools (namely, github and whatever client software) and get a login
at some site (github). Some might not have used git. A few might not
have used any code repository system. A wiki on the other hand can be
edited by anyone who can type stuff into a web form and can be
configured not to require a login (ala Wikipedia itself).
--
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, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--
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, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
