On Sun, May 17, 2009 at 8:22 AM, Grant Rettke <[email protected]> wrote: > You dove deep into these topics and have covered just how tricky it > would be. It would be really interesting for the readers for you to > take what you have learned and write a summary article about how to > write code that most of the time will basically avoid this trickiness. > > Is it as simple as "Don't write libraries that rely on side-effects > and adhere to the R6RS spec?", or is it more?
Of course "avoid side effects" is a good advice, but I wanted to document *why* it is a good advice and what are the risks you may incur into if you do not follow it. Plus, sometimes you really want to keep a global registry working across modules and I do not see how to implement it without side effects.
