From: Damien Doligez <damien.doligez@inria.fr>
To: caml Caml <caml-list@inria.fr>
Subject: Re: [Caml-list] Are map and iter guaranteed to be called in forwards order?
Date: Tue, 17 Aug 2004 14:45:37 +0200 [thread overview]
Message-ID: <56BE253C-F04B-11D8-A3E6-00039310CAE8@inria.fr> (raw)
In-Reply-To: <20040817120053.GA9749@annexia.org>
On Aug 17, 2004, at 14:00, Richard Jones wrote:
> Are the map and iter[1] functions guaranteed to be called in the
> expected order?
iter: yes
map: no
-- Damien
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-08-17 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 12:00 Richard Jones
2004-08-17 12:45 ` Damien Doligez [this message]
2004-08-17 14:26 ` John Prevost
2004-08-17 14:56 ` Richard Jones
2004-08-17 15:13 ` Anil Madhavapeddy
2004-08-17 15:17 ` Jean-Marie Gaillourdert
2004-08-17 15:19 ` John Prevost
2004-08-18 0:57 ` Jon Harrop
2004-08-18 5:11 ` skaller
2004-08-18 7:10 ` skaller
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=56BE253C-F04B-11D8-A3E6-00039310CAE8@inria.fr \
--to=damien.doligez@inria.fr \
--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).