A few things:
--clojure does not do automatic TCO, so you might want to look at
recur to handle your stack issue
--recur won't work unless you rewrite your function so that the
recursive call is in tail position
--you probably can do that rewrite by passing around the levenshtein
grid as an accumul
@Mark, yeah, I meant using the bottom-up approach and passing that
matrix as the accumulator. (I thought that I remembered seeing such an
implementation in the goopy library, but when I looked today I didn't
find any lev implementation at all.)
@Christian, yes, I missed the point of your question.
On Mar 25, 6:54 am, ultranewb wrote:
> On another note, I have unfortunately decided that I just can't do
> Clojure right now.
I have been reading usenet for 20+ years, and this whole thread just
became one of the most epic trolls I have ever seen.
--
You received this message because you ar
On Mar 28, 9:18 am, Ken Wesson wrote:
> On the other hand, there's a definite contingent that do hold
> newbs in low esteem and are deliberately rude to them, regarding them
> as low-status individuals on the techno totem pole. Why does this type
> bother to reply to newbie questions at all?
(Al
I have an issue that I think is related to laziness, but I am not sure
I understand where the problem lies.
Let's say I have tabular data in a sequence of sequences. I get the
second column of the table like this:
(map #(nth % 1) my-table)
I can do some sequence things directly to the list retur
error had to come from somewhere.)
For the record, here is how I build the table:
(def data (slurp "data.txt"))
(def lines (. data split "\n"))
(def my-table (map #(. % split "\t") lines))
On Oct 25, 9:28 am, Ken Wesson wrote:
> On Oct 24, 11:46 pm, Tim Webste
f the variables in any way as I was experimenting, but
now that seems like the most likely explanation.
On Oct 25, 2:42 pm, Jürgen Hötzel wrote:
> 2010/10/25 Tim Webster :
>
> > I thought that the issue might be that the concrete data still was not
> > populated in my list-of-lists, un
