From: John Max Skaller <skaller@maxtal.com.au>
To: Jeremy Fincher <tweedgeezer@hotmail.com>
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] High level (asynchronous) networking library?
Date: Sat, 14 Jul 2001 12:29:45 +1000 [thread overview]
Message-ID: <3B4FAE99.8447FFEE@maxtal.com.au> (raw)
In-Reply-To: <F122M3oryKFRJrzdDW60000ab1d@hotmail.com>
Jeremy Fincher wrote:
> Someone has written "asyncore turned inside out" using Stackless Python, an
> implementation of Python that has first-class continuations) using
> continuations to implement the apparent multi-tasking. It apparently (I've
> not used it myself) makes the asynchronous networking part of the coding a
> little more transparent to the user than asyncore does. I'm curious if
> something similar could be implemented in O'Caml with closures, and if it
> could achieve similar user-transparency.
If you want to do this with an Ocaml like language,
consider Felix, which I'm developing at present. It uses heap
allocated stack frames, like Stackless Python, and operates
by continuation passing. Unlike Stackless, it generates native
code (via C++), and functions still use the machine stack
So it should be much faster than Stackless, while supporting
a strongly typed language with first class functions.
--
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
New generation programming language Felix http://felix.sourceforge.net
Literate Programming tool Interscript
http://Interscript.sourceforge.net
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
prev parent reply other threads:[~2001-07-14 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 5:31 Jeremy Fincher
2001-07-12 9:06 ` Markus Mottl
2001-07-12 12:14 ` Jeremy Fincher
2001-07-15 7:26 ` Ohad Rodeh
2001-07-12 20:37 ` Gerd Stolpmann
2001-07-14 2:29 ` John Max Skaller [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B4FAE99.8447FFEE@maxtal.com.au \
--to=skaller@maxtal.com.au \
--cc=caml-list@pauillac.inria.fr \
--cc=tweedgeezer@hotmail.com \
/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 NNTP newsgroup(s).