caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eray Ozkural <examachine@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Purity and lazyness
Date: Fri, 7 Jan 2011 22:33:58 +0200	[thread overview]
Message-ID: <AANLkTi=m5g=gfOpOTQxeOW0WvkGh-hNDJE9S5PfXMvi2@mail.gmail.com> (raw)
In-Reply-To: <7B166A75-88A4-41BC-A26F-A2CC8B6E30FC@ezabel.com>

[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]

No, I don't think so.

I think these:
http://csg.csail.mit.edu/pubs/haskell.html
http://csg.csail.mit.edu/projects/languages/ph.shtml

What a cool research group, combines two of my research interests as well :)

Best,

On Fri, Jan 7, 2011 at 10:29 PM, <orbitz@ezabel.com> wrote:

> I believe you are thinking of 'Timber'?
>
>
>
> On Jan 7, 2011, at 3:22 PM, Eray Ozkural wrote:
>
>  On Fri, Jan 7, 2011 at 6:38 PM, David Rajchenbach-Teller <
>> David.Teller@univ-orleans.fr> wrote:
>> Correct me if I'm wrong, but I wouldn't classify Erlang as "pure": sending
>> and receiving messages -- which are two of the most important primitives in
>> Erlang -- are definitely side-effects.
>> Also, asynchronous error-checking, Mnesia, etc. look quite impure to me.
>>
>> I also vaguely remember Simon Peyton-Jones declaring something along the
>> lines of "The next Haskell will be strict".
>>
>>
>> There was a strict compiler for Haskell, whatever happened to it? Most
>> times I found it cumbersome to deal with the performance effects of default
>> laziness.
>>
>> Best,
>>
>> --
>> Eray Ozkural, PhD candidate.  Comp. Sci. Dept., Bilkent University, Ankara
>> http://groups.yahoo.com/group/ai-philosophy
>> http://myspace.com/arizanesil http://myspace.com/malfunct
>>
>>
>


-- 
Eray Ozkural, PhD candidate.  Comp. Sci. Dept., Bilkent University, Ankara
http://groups.yahoo.com/group/ai-philosophy
http://myspace.com/arizanesil http://myspace.com/malfunct

[-- Attachment #2: Type: text/html, Size: 2590 bytes --]

  parent reply	other threads:[~2011-01-07 20:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 15:35 Dario Teixeira
2011-01-07 16:07 ` Damien Doligez
2011-01-07 16:38   ` David Rajchenbach-Teller
2011-01-07 18:16     ` Holger Weiß
2011-01-07 20:22     ` Eray Ozkural
2011-01-07 20:29       ` orbitz
2011-01-07 20:30         ` Joel Reymont
2011-01-07 20:33         ` Eray Ozkural [this message]
2011-01-08  9:44     ` Jesper Louis Andersen
2011-01-07 17:21 ` Alain Frisch
2011-01-07 17:46   ` Christophe Raffalli
2011-01-07 18:11 ` Holger Weiß
2011-01-07 18:52   ` Brian Hurt
2011-01-07 19:32     ` Petter Urkedal
2011-01-07 20:25     ` Eray Ozkural
2011-01-09 16:11     ` Jon Harrop
2011-01-10  6:27       ` Eray Ozkural
2011-01-07 19:17 ` Florian Weimer
     [not found]   ` <AANLkTikxCSQ+0XkOmSVDb3EWq_2oQ0pac3bDgc7f7jq+@mail.gmail.com>
2011-01-07 20:52     ` bluestorm
2011-01-09 16:15       ` Jon Harrop
2011-01-08  0:26   ` Elias Gabriel Amaral da Silva
2011-01-08  9:28     ` Christophe Raffalli
2011-01-08 22:47     ` Florian Weimer
2011-01-09 10:00       ` Petter Urkedal

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='AANLkTi=m5g=gfOpOTQxeOW0WvkGh-hNDJE9S5PfXMvi2@mail.gmail.com' \
    --to=examachine@gmail.com \
    --cc=caml-list@inria.fr \
    /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).