Rich, I'm currently working on some code where I'm implementing state machines where each state is a function. To move to another state, the current state returns the function of the next state and trampoline runs the machine through to completion. My next step is to have each state return a value in addition to the function for the next state, and the result from running the state machine will be a list of values from each state. Writing a specific trampoline to extract the list of return values and call the next state function in a lazy manner is easy to implement.
As you say, this is an of-a-piece design, so I would vote that trampoline itself should be kept cruft-free. My $.02 Jim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
