The Scheme community wiki is far from being the best resource for looking up the answers to the exercises. Eli Bendersky has a good page with answers written in Common Lisp:
Also, if you throw "sicp exercise x.yz solution" into Google, a couple of other blogs will pop up frequently - it is best to always consult different sources, sometimes some of the posted "solutions" are a bit confused, or at least not discussed clearly enough.
After you get used to some basic FP idioms, the exercises aren't really that hard, especially if you had at least the most basic exposure to the topics the programs in the book touch (circuits, elementary higher math etc., remember it was a part of the beginning EE/CS curriculum). There are just a few common causes of confusion and problems with the exercises that are very well summarized in the paper "Why calculating is better then scheming":
Another thing is that when the programs in the book start to become larger, it becomes harder and harder to work with them, it's basically hundreds of functions in a single long file. Using some stronger form of modularization throughout the book would help a lot, at least from the moment they already have explained how one can achieve it (they describe message-passing etc.).
http://github.com/sztywny/sicp
The Scheme community wiki is far from being the best resource for looking up the answers to the exercises. Eli Bendersky has a good page with answers written in Common Lisp:
http://eli.thegreenplace.net/category/programming/lisp/sicp/
Also, if you throw "sicp exercise x.yz solution" into Google, a couple of other blogs will pop up frequently - it is best to always consult different sources, sometimes some of the posted "solutions" are a bit confused, or at least not discussed clearly enough.
After you get used to some basic FP idioms, the exercises aren't really that hard, especially if you had at least the most basic exposure to the topics the programs in the book touch (circuits, elementary higher math etc., remember it was a part of the beginning EE/CS curriculum). There are just a few common causes of confusion and problems with the exercises that are very well summarized in the paper "Why calculating is better then scheming":
http://www.cs.kent.ac.uk/people/staff/dat/miranda/wadler87.p...
Another thing is that when the programs in the book start to become larger, it becomes harder and harder to work with them, it's basically hundreds of functions in a single long file. Using some stronger form of modularization throughout the book would help a lot, at least from the moment they already have explained how one can achieve it (they describe message-passing etc.).