From: Radu Grigore <radugrigore@gmail.com>
To: Jon Harrop <jon@jdh30.plus.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] C++ STL and template features compared with OCaml parametric polymorphism and OO features
Date: Mon, 27 Sep 2004 16:31:00 +0300 [thread overview]
Message-ID: <7f8e92aa04092706317dae6556@mail.gmail.com> (raw)
In-Reply-To: <200409271411.30384.jon@jdh30.plus.com>
On Mon, 27 Sep 2004 14:11:30 +0100, Jon Harrop <jon@jdh30.plus.com> wrote:
> > For the writter of the function there is a big difference, especially
> > if it has to write the specialized versions.
>
> The equivalent to the writer of fold is the writer of an iterator. You have to
> write specialized versions for each type of iterator just as you would have
> to write your own fold.
That's why I said iterators are another level of abstraction. The
difference is that after you write the iterators code for a new
sequence-like data structure all the "generic" functions, not only
fold but also map and others, will automagically work on them. The
simplest form of an "iterator" is implementing a "next" function for
all sequences (although in this situation it is more of an
"enumeration").
You should really check out the article cited by Vasili. It seems that
we understend different things by "functional equivalent of an
iterator", since you talk about the advantage of being able of going
backwards a.s.o. which really is an irrelevant advantage.
regards,
radu
-------------------
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-09-27 13:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 21:12 Vasili Galchin
2004-09-25 21:38 ` Nicolas Cannasse
2004-09-25 22:15 ` Vasili Galchin
2004-09-25 22:52 ` Vasili Galchin
2004-09-26 1:34 ` Jon Harrop
2004-09-26 5:31 ` Radu Grigore
2004-09-26 9:47 ` sejourne_kevin
2004-09-26 13:05 ` Jon Harrop
2004-09-26 14:36 ` skaller
2004-09-26 15:08 ` sejourne_kevin
2004-09-26 15:27 ` skaller
2004-09-26 18:51 ` Jon Harrop
2004-09-26 20:14 ` Radu Grigore
2004-09-27 1:59 ` Jon Harrop
2004-09-27 4:48 ` skaller
2004-09-27 9:40 ` Jacques GARRIGUE
2004-09-27 10:50 ` Radu Grigore
2004-09-27 12:14 ` skaller
2004-09-27 13:11 ` Jon Harrop
2004-09-27 13:31 ` Radu Grigore [this message]
2004-09-27 16:54 ` Jon Harrop
2004-09-29 18:59 ` Radu Grigore
2004-09-27 13:32 ` Radu Grigore
2004-09-27 14:04 ` Brian Hurt
2004-09-27 14:58 ` skaller
2004-09-27 15:30 ` Brian Hurt
2004-09-27 16:38 ` skaller
2004-09-27 17:01 ` Brian Hurt
2004-09-28 1:21 ` skaller
2004-09-27 16:41 ` brogoff
2004-09-28 0:26 ` skaller
2004-09-29 15:32 ` Florian Hars
2004-09-29 16:49 ` [Caml-list] Factoring HOFs [was Re: C++ STL...] Jon Harrop
2004-09-30 9:19 ` Radu Grigore
2004-09-30 10:13 ` Keith Wansbrough
2004-09-30 10:31 ` Keith Wansbrough
2004-09-30 13:21 ` skaller
2004-09-30 23:17 ` [Caml-list] Factoring HOFs Jacques Garrigue
2004-10-01 8:46 ` Keith Wansbrough
2004-10-01 17:35 ` brogoff
2004-09-26 20:43 ` [Caml-list] C++ STL and template features compared with OCaml parametric polymorphism and OO features skaller
2004-09-26 14:19 ` 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=7f8e92aa04092706317dae6556@mail.gmail.com \
--to=radugrigore@gmail.com \
--cc=caml-list@inria.fr \
--cc=jon@jdh30.plus.com \
/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