caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Tore Lund <tl001@online.no>
To: caml-list@inria.fr
Cc: Sebastien Carlier <sebastien@posse42.net>
Subject: Re: [Caml-list] Evaluation Order
Date: Sun, 10 Jun 2001 15:11:10 +0200	[thread overview]
Message-ID: <3B2371EE.A4FF2E51@online.no> (raw)
In-Reply-To: <3B235796.73CA31A@online.no>

Tore Lund wrote:
> 
>   # let _ =
>       print_string "before";
>       print_string "MIDDLE";
>       print_string "after";;
>   beforeMIDDLEafter- : unit = ()
> 
>   # let _ =
>       print_string "before";
>       Format.print_string "MIDDLE";
>       print_string "after";;
>   beforeafterMIDDLE- : unit = ()
> 
> What's going on here?  All I did was to add "Format".  Is not printing
> an "effet du bord"?

For that matter:

  # let a =  print_string "before" in
    let b =  print_string "MIDDLE" in
    let c =  print_string "after" in
    a; b; c;;
  beforeMIDDLEafter- : unit = ()

versus:

  # let a = print_string "before" in
    let b = Format.print_string "MIDDLE" in
    let c = print_string "after" in
    a; b; c;;
  beforeafterMIDDLE- : unit = ()

Okay.  So there is buffering at work that has little to do with OCaml. 
Which probably means that the only side-effects guaranteed to happen in
a certain order are those carried out by the runtime system itself. 
Hmmm, at the very least this makes it necessary to distinguish between
two species of side-effect.
-- 
    Tore

-------------------
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-10 13:12 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 [this message]
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
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=3B2371EE.A4FF2E51@online.no \
    --to=tl001@online.no \
    --cc=caml-list@inria.fr \
    --cc=sebastien@posse42.net \
    /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).