Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Eray Ozkural <examachine@gmail.com>
To: Brian Hurt <bhurt@spnz.org>
Cc: "Holger Weiß" <holger@cis.fu-berlin.de>,
	"Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] Purity and lazyness
Date: Fri, 7 Jan 2011 22:25:36 +0200	[thread overview]
Message-ID: <AANLkTikBM9qbkCB8DtteM11E_NJ81bbbMFMsyGcu1o-i@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101071344150.7793@sergyar>

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

On Fri, Jan 7, 2011 at 8:52 PM, Brian Hurt <bhurt@spnz.org> wrote:

>
>
> On Fri, 7 Jan 2011, Holger Weiß wrote:
>
>  Simon Peyton-Jones argues like this:
>>
>> | Because Haskell is lazy it meant that we were much more consistent about
>> | keeping the language pure.  You could have a pure, strict, call by value
>> | language, but no one has managed to do that because the moment you have
>> | a strict call by value language, the temptation to add impurities (side
>> | effects) is overwhelming.  So "laziness kept us pure" is the slogan!
>>
>> [
>> http://www.techworld.com.au/article/261007/a-z_programming_languages_haskell/?pp=7]
>>
>>
> Unless there is some other driver to keep things pure even while being
> strict.  And I would argue there is- concurrency.  Concurrency has a lot of
> similarities with laziness, in that the ordering of computations can be (and
> often is) undefined, with all the fun that entails.  Haskell is really good
> at multithreaded because it has already "paid the price" of dealing with
> asynchronous computations.


Seconded. And probably more advanced compilers could make better decisions
at optimizing parallel execution.

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

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

  parent reply	other threads:[~2011-01-07 20:25 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
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 [this message]
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=AANLkTikBM9qbkCB8DtteM11E_NJ81bbbMFMsyGcu1o-i@mail.gmail.com \
    --to=examachine@gmail.com \
    --cc=bhurt@spnz.org \
    --cc=caml-list@inria.fr \
    --cc=holger@cis.fu-berlin.de \
    /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