Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: John Skaller <skaller@maxtal.com.au>
To: Andrew Kennedy <akenn@microsoft.com>,
	"'Markus Mottl'" <mottl@miss.wu-wien.ac.at>,
	caml-list@inria.fr
Subject: RE: optimization and purity
Date: Sat, 24 Jul 1999 22:45:41 +1000	[thread overview]
Message-ID: <3.0.6.32.19990724224541.0096ac40@mail.triode.net.au> (raw)
In-Reply-To: <7CD674FF54FBD21181D800805F57CD5488B073@RED-MSG-44>

At 08:48 23/07/99 -0700, Andrew Kennedy wrote:
>> -----Original Message-----
>> From: Markus Mottl [mailto:mottl@miss.wu-wien.ac.at]
>> Subject: optimization and purity
>> 
>> I would like to know whether anyone has already thought about means of
>> indicating or inferring purity of functions.
>> 

>You are indeed correct that knowing the purity of functions would permit a
>number of optimisations such as the loop-hoisting example you present. 

	Actually, I'm quite interested in the same thing
from a different angle: rather than being concerned with
_compiler_ code optimisation, I'm concerned with human ability
to reason about code: ocaml loses the simplicity of reasoning about
derived from referential transparency available in 'pure' functional
languages. (But of course the two things are strongly related)

-------------------------------------------------------
John Skaller    email: skaller@maxtal.com.au
		http://www.maxtal.com.au/~skaller
		phone: 61-2-96600850
		snail: 10/1 Toxteth Rd, Glebe NSW 2037, Australia





  parent reply	other threads:[~1999-07-27  1:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-23 15:48 Andrew Kennedy
1999-07-23 17:49 ` Simon Helsen
1999-07-23 21:37 ` Pierre Weis
1999-07-24 12:45 ` John Skaller [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-07-18 18:57 Markus Mottl

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=3.0.6.32.19990724224541.0096ac40@mail.triode.net.au \
    --to=skaller@maxtal.com.au \
    --cc=akenn@microsoft.com \
    --cc=caml-list@inria.fr \
    --cc=mottl@miss.wu-wien.ac.at \
    /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