1. I think the segfault is explored in this thread: http://article.gmane.org/gmane.lisp.scheme.gambit/7068/match=xcode+5 http://article.gmane.org/gmane.lisp.sch

1. I think the segfault is explored in this thread: http://article.gmane.org/gmane.lisp.scheme.gambit/7068/match=xcode+5 http://article.gmane.org/gmane.lisp.scheme.gambit/7068/match... Basically, the problem is with the version of llvm/clang that Apple uses in Xcode 5. Some of the newer Xcode betas might fix it. I personally use the Xcode 4 compiler. You could probably also build your own clang from their SVN. For more info you could probably ask the mailing list. 2. I definitely looked at chicken, and I can't remember my exact reason for going with gambit, but it was a practical one. I don't think I could get chicken up and running on the iphone for some reason. Chicken did seem to be better documented with better libraries. Gambit may be faster though. (I started working on this about a year ago. The situation may be completely different now.) My game isn't too complex, compared to, say, a first person shooter. I'm not sure if the GC implementation would start to matter in that circumstance. I recommend trying one and then if you're happy with it, great. If not, most of the code will be portable. 3. No. I don't have much experience with them (besides learning the basics in school). I did use a lot of closures, anonymous lambdas, and lambda builder functions. Glad you're enjoying the game!