From: Alan Grover <awgrover@mail.msen.com>
Cc: guile-user@gnu.org
Subject: Re: mod_lisp for guile
Date: Fri, 16 Dec 2005 08:21:10 -0500 [thread overview]
Message-ID: <43A2BF46.4090407@mail.msen.com> (raw)
In-Reply-To: <87y82mt09c.fsf@ossau.uklinux.net>
Neil Jerram wrote:
> Alan Grover <awgrover@mail.msen.com> 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
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-12-16 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 17:25 mod_lisp for guile Alan Grover
2005-09-16 18:46 ` Neil Jerram
2005-09-19 14:46 ` Alan Grover
2005-09-19 21:32 ` Neil Jerram
2005-09-20 3:24 ` Alan Grover
2005-09-20 4:44 ` Threads (was: mod_lisp for guile) Tomas Zerolo
2005-09-20 12:12 ` Threads Alan Grover
2005-12-04 10:07 ` mod_lisp for guile Neil Jerram
2005-12-05 17:21 ` Alan Grover
2005-12-15 23:21 ` Neil Jerram
2005-12-16 13:21 ` Alan Grover [this message]
2005-12-29 10:18 ` Neil Jerram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43A2BF46.4090407@mail.msen.com \
--to=awgrover@mail.msen.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).