Neil Jerram wrote: > Alan Grover <[EMAIL PROTECTED]> writes: >>The lazy-ness is really in taking advantage of patterns for list >>processing. Perhaps I didn't give an example like: >> (define list-of-http-transactions (mod_lisp some-port-listener)) >> (for-each handle-request list-of-http-transactions) > > > That's kind of neat, but doesn't actually feel very natural to me. > When I have socket input to deal with, I typically want (or rather > need) to select on the socket along with other stuff, and then > dispatch the next request when select indicates data available. I > don't see how that could naturally be rewritten in terms of list > operations, or that it would be helpful to do so.
Could you talk a little bit more about the "select with other stuff" pattern? What kind of stuff? > Yes, indeed. Guile does come with a lazy list library, though - have > you seen (ice-9 streams)? I don't think I've looked at it yet. _______________________________________________ Guile-user mailing list [email protected] http://lists.gnu.org/mailman/listinfo/guile-user
