Kyle R. Burton on 15 Jun 2008 13:50:45 -0700


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Review? (Fuzzy String example code)

  • From: "Kyle R. Burton" <kyle.burton@gmail.com>
  • To: philly-lambda@googlegroups.com
  • Subject: Review? (Fuzzy String example code)
  • Date: Sun, 15 Jun 2008 16:50:31 -0400
  • Authentication-results: mx.google.com; spf=pass (google.com: domain of kyle.burton@gmail.com designates 209.85.200.170 as permitted sender) smtp.mail=kyle.burton@gmail.com; dkim=pass (test mode) header.i=@gmail.com
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:received:x-sender:x-apparently-to :received:received:received-spf:authentication-results:received :dkim-signature:domainkey-signature:received:received:message-id :date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition:reply-to:sender :precedence:x-google-loop:mailing-list:list-id:list-post:list-help :list-unsubscribe:x-beenthere; bh=G/V3cjwhMoIEG1o/VvO+wHr0enAcvoX7mlfOsRMAsbI=; b=VDwaexi0HKDx6UTZkTYPxfIZo2Z6Rjr/3EGHSaOKHAPBYnyPq9JyLAhzOJOtf0qn4h +GaEX2f7ml75egq6JjSIc+1ZW/vZwnBGbc39qmnLAFu3j/6lnFRGnXvnCOt7g6I/t6yC OAmWV1663DT2OwDj81+JCyCgBDTKW1i0LmlUE=
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=bFI2HrN4NBm8ek+7fDGnplYbcHvb1zEAfSfPAaOxTGU=; b=RbeS6Dtr6dnYLpcrxCFA1EotZU4/b4PrkOUE9t3UWIDHN27JVhnm1VdnA3OM8etjxH 4hJOLPvcqij0yGqTORk9GTKJGjC9VhCp1dUNtiZ/1hUZa60S43nLYHZTNbfBoN3DtlHZ kfbvDhBFDvgB9Y5idorF9Bwh17tWtD4h5Z+1E=
  • Mailing-list: list philly-lambda@googlegroups.com; contact philly-lambda-owner@googlegroups.com
  • Reply-to: philly-lambda@googlegroups.com
  • Sender: philly-lambda@googlegroups.com

Anyone willing to help me out? I'm looking for, in general, a second
(or n-th) pair of eyes for the code for the Fuzzy String talk.  Most
of it is Scheme (Chicken), a smaller bit is C.

What I'm looking for is standard code review style feedback.  To find
things like: glaring mistakes; non-idiomatic-ness; comments on the
readability / ease of understanding; or any other suggestions you may
have wrt the talk.  I don't plan on using most of this during the
talk, but it may come up when doing some examples.

To run the code you'll need chicken installed:
http://www.call-with-current-continuation.org/, and several 'eggs',
which you can install using chicken-setup: levenshtein, metaphone,
regex-literals.  The code will bitch at you for any that I'm
forgetting.  There are a couple of shell scripts for running various
parts of the source tree that will hopefully make sense if you decide
to try it out.  There is 1 hard-coded path in src/chicken/find.scm to
the lnames.txt file which I haven't parameterized yet.

This was a lot easier on Linux than it was on OS X.  On OS X (using
port), I had to install gmp (for the numbers egg, I had already had it
under Linux), then do

  chicken-setup -csc-option "-L/opt/local/lib -I/opt/local/include" numbers

to get the numbers egg to install.  Also, I had to make a change to
the textBrew/Makefile - change .so to .dylib, and -shared to -dylib
for the CC option.  Hrm..maybe all this should go into a readme.

I'm still working on the slides.

The slides and code can be gotten here:

  http://asymmetrical-view.com/talks/fuzzy-string.tar.gz
  http://asymmetrical-view.com/talks/fuzzy-string/


Thanks,


Kyle