Thanks Noah and Per; English language is more difficult than scheme language for me. :( I want to share my code or modification to others and learn somethings during that.
Few days ago, I found testing.scm, the reference implementation of SRFI 64, does not pass srfi-64-test.scm, a test suite for the SRFI 64, on Guile 2.0. The cause is defining test-apply before defining test-with-runner in testing.scm. I did not realize it then and try to understand how testing.scm work. I'll attatch two files on this mail; srfi-64.scm.gz and testing.patch.gz. The srfi-64.scm.gz file is for Guile, Chicken and Gambit users. The testing.patch.gz file is for Per. 2012/4/20 Per Bothner <p...@bothner.com> > On 04/19/2012 07:50 PM, Noah Lavine wrote: >> >> I'm a bit confused by this conversation. Do you want to merge this >> code into Guile, or into the reference implementation of SRFI 64? >> > If it's into Guile, I'll feel happy. If it's of helpful to Per, I'll feel happy too. Unfortunately, this Guile port seems like a complete rewrite: > The diff (relative to the reference implementation) is over twice as big > as than the original reference implementation! > Humm.... Even after applying patch, testing.scm is not same to srfi-64.scm because of the order and style of definitions. The order of definitions, I fixed testing.scm for on Guile but not on Chicken. The srfi-64.scm can be compiled and loaded by module on Chicken.
srfi-64.scm.gz
Description: GNU Zip compressed data
testing.patch.gz
Description: GNU Zip compressed data
