On 12/2/06, Donald Bruce Stewart <[EMAIL PROTECTED]> wrote:
> WASH has one, and I uploaded mine to http://www.taral.net/mime.tar.gz
> for people to look at and use.
Are these now documented on haskell.org's libraries page?
http://haskell.org/haskellwiki/Libraries_and_tools
WASH should be.
taralx:
> On 12/2/06, Jeremy Shaw <[EMAIL PROTECTED]> wrote:
> >In any case, I wanted to release this library now since I know other
> >people are already duplicating some (all?) of the work :) I am quite
> >happy to accept patches. If someone else has a better code base
> >already, I am happy to j
On 12/2/06, Jeremy Shaw <[EMAIL PROTECTED]> wrote:
In any case, I wanted to release this library now since I know other
people are already duplicating some (all?) of the work :) I am quite
happy to accept patches. If someone else has a better code base
already, I am happy to jump ship and work on
Hello,
I would like to announce the availability of my partially complete
MIME processing library. This library is supposed to be able to parse
emails and decode various attachments, and generate emails with
attachments.
The library includes modules that implement portions of:
RFC 2045 - Multip
Cat Dancer wrote:
> On 12/2/06, Chris Kuklewicz <[EMAIL PROTECTED]> wrote:
>> Hi, I have taken a crack at this. The best thing would be not to use the
>> asynchronous exceptions to signal the thread that calls accept.
>
> I'd certainly be most happy not to use asynchronous exceptions as the
> sig
On 12/2/06, Chris Kuklewicz <[EMAIL PROTECTED]> wrote:
Hi, I have taken a crack at this. The best thing would be not to use the
asynchronous exceptions to signal the thread that calls accept.
I'd certainly be most happy not to use asynchronous exceptions as the
signalling mechanism, but how wo
Hi, I have taken a crack at this. The best thing would be not to use the
asynchronous exceptions to signal the thread that calls accept. And use STM
more, since the exception semantics are much easier to get right.
But a few minor changes gets closer to what you want. First, the main problem
yo
I'd like to write a server accepting incoming network connections that
can be gracefully shutdown.
When the server is asked to shutdown, it should stop accepting new
connections, finish processing any current connections, and then
terminate.
Clients can retry if they attempt to make a connection
Am Freitag, 1. Dezember 2006 21:37 schrieb Krasimir Angelov:
> [...]
> do allocConsole
> .
> .
> putStrLn "Hello, world!"
> .
> .
> freeConsole
> [...]
Having explicit alloc/free pairs can lead to resource leaks in the presence of
exceptions. Simple s
