Evan Hanson scripsit: > There's not much that's obviously missing anymore, it's mostly rough > edges as you said. The list at https://wiki.call-cc.org/r7rs-tasks#todo > is up to date.
I've added a few things there. The only substantive point is that after doing (use r7rs) in the REPL, the (scheme base) library should be loaded. Currently it isn't, which means that (e.g.) you get the non-numbers version of `/`. > Actually, the most important todo is probably documentation of the > gotchas/limitations/interplay between the egg and core that aren't > obvious from that list, e.g. `(import (foo bar))` doesn't load code > from ./foo/bar.scm (or ".sld" as seems to have become common), one must > `(import-for-syntax (r7rs))` to get R7RS's syntax-rules, and so on. But, > overall, I'd be fine with releasing it with such disclaimers just so > people can start hacking at it. +1. Why are the R7RS library names like (foo bar) mapped to foo.bar instead of foo-bar? -- John Cowan http://www.ccil.org/~cowan [email protected] Original line from The Warrior's Apprentice by Lois McMaster Bujold: "Only on Barrayar would pulling a loaded needler start a stampede toward one." English-to-Russian-to-English mangling thereof: "Only on Barrayar you risk to lose support instead of finding it when you threat with the charged weapon." _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
