Path: utzoo!attcan!uunet!decwrl!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!silver!jashley
From: jashley@silver.ucs.indiana.edu (J. Michael Ashley)
Newsgroups: comp.lang.functional
Subject: Re: side effects in FL's (was "Can laziness sometimes be too lazy?")
Message-ID: <52063@iuvax.cs.indiana.edu>
Date: 25 Jul 90 16:50:08 GMT
References: <51915@iuvax.cs.indiana.edu> <5303@castle.ed.ac.uk>
Sender: news@iuvax.cs.indiana.edu
Organization: Graceland
Lines: 22

In article <5303@castle.ed.ac.uk> nick@lfcs.ed.ac.uk (Nick Rothwell) writes:
>In article <51915@iuvax.cs.indiana.edu>, jashley@silver (J. Michael Ashley) writes:
>>has implemented it in the language.  It's now in the standard.
>* W R O N G ! *
>Read the Standard (published by MIT) and tell me where you see it.

Sorry about that.  My facts were second hand.  Didn't mean to light the
fireworks!  :-)

>Callcc is not part of Standard ML.

I guess I was being too optimistic.

>It's an extension implemented by
>the New Jersey ML implementors, as is the separate compilation scheme
>implemented by us, the exception continuation handling scheme
>implemented by Reppy, and so on.

Thanks everybody for settin' me straight.

mike ashley
jashley@lanl.gov