caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Dave Mason <dmason@sarg.Ryerson.CA>
To: caml-list@inria.fr
Cc: John Max Skaller <skaller@ozemail.com.au>,
	David McClain <dmcclain1@mindspring.com>,
	Brian Rogoff <bpr@best.com>
Subject: Re: [Caml-list] Evaluation Order
Date: Sun, 10 Jun 2001 13:27:08 -0400	[thread overview]
Message-ID: <200106101727.NAA09290@sarg.Ryerson.CA> (raw)
In-Reply-To: Your message of "Sun, 10 Jun 2001 09:47:25 PDT." <Pine.BSF.4.21.0106100935390.29219-100000@shell5.ba.best.com>

>>>>> On Sun, 10 Jun 2001 09:47:25 -0700 (PDT), Brian Rogoff <bpr@best.com> said:

> Well, OCaml isn't referentially transparent, and it is strict to
> begin with. I agree that it would be awful if my argument was only
> about the order of evaluation of (+).

No it isn't.  But it would be nice if code which wasn't was detectable
as such and otherwise you could reason as if it were.  I have a
longish email on its way to the list that proposes marking the results
of any functions that cause side-effects as such, and not allowing
them to be used in compound expressions where they would be
order-dependent.

> Why not make the default correspond to everyone's intuition?

Because that isn't everyone's intuition!  Better to not specify the
order, but prevent expressions where order dependency could create a
problem.  That also leaves the compiler maximum flexibility in
ordering evaluation (while this may not be exploited by the current
compilers, it is likely to become increasingly important as the
processor/memory differential increases).

> I agree completely. I even shove in prints to debug purely
> functional code (shame on me!) by adding "let _ = prerr_endline
> ... in" in such constructs.

I sometimes do that.  Perhaps for my proposal it would be useful to
have a ``debugf'' that prints (and flushes) to stderr, but isn't
flagged as side-effecting, with the assumption that these are not part
of the semantics of the program and will be removed before production.

(BTW, my postings to this list usually take 2 days to appear... I just
checked and this machine's mail queue is empty, so I don't know which
machine is holding on to my posting.... but I wish it would stop!)

../Dave
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  reply	other threads:[~2001-06-11 11:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-09 15:59 David McClain
2001-06-09 20:17 ` Brian Rogoff
2001-06-09 23:12   ` David McClain
2001-06-09 23:28     ` David McClain
2001-06-10  1:04       ` Dave Mason
2001-06-10  2:25         ` David McClain
2001-06-11 13:03           ` Dave Mason
2001-06-12 17:55             ` John Max Skaller
2001-06-13 16:54               ` Frederick Smith
2001-06-13 21:43                 ` John Max Skaller
2001-06-10  1:06       ` Charles Martin
2001-06-10  2:27         ` David McClain
2001-06-10 11:18         ` Tore Lund
2001-06-10 13:11           ` Tore Lund
2001-06-10 14:31           ` John Max Skaller
2001-06-12 15:12             ` Pierre Weis
2001-06-10 10:40       ` Joerg Czeranski
2001-06-10 14:06       ` John Max Skaller
2001-06-11 12:59         ` Dave Mason
2001-06-12 17:34           ` John Max Skaller
2001-06-10 13:47   ` John Max Skaller
2001-06-10 16:47     ` Brian Rogoff
2001-06-10 17:27       ` Dave Mason [this message]
2001-06-12 16:10       ` John Max Skaller
2001-06-09 23:19 ` John Max Skaller
2001-06-10  2:44 David McClain
2001-06-10  2:48 ` Patrick M Doane
2001-06-10  5:51   ` David McClain
2001-06-10 17:59 Damien Doligez
2001-06-10 18:28 ` Dave Mason
2001-06-15 17:00 Manuel Fahndrich
2009-06-14 16:36 evaluation order Christophe Raffalli
2009-06-14 19:40 ` [Caml-list] " Jon Harrop
2009-06-14 21:12   ` Christophe Raffalli

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=200106101727.NAA09290@sarg.Ryerson.CA \
    --to=dmason@sarg.ryerson.ca \
    --cc=bpr@best.com \
    --cc=caml-list@inria.fr \
    --cc=dmcclain1@mindspring.com \
    --cc=skaller@ozemail.com.au \
    /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).