From: Francois Pottier <francois.pottier@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: generic programming
Date: Mon, 8 Jul 2002 11:54:53 +0200 [thread overview]
Message-ID: <20020708115453.A32472@pauillac.inria.fr> (raw)
In-Reply-To: <4.1.20020706000345.009f9610@pop3.btclick.com>; from daveb@tardis.ed.ac.uk on Sat, Jul 06, 2002 at 12:05:30AM +0100
On Sat, Jul 06, 2002 at 12:05:30AM +0100, Dave Berry wrote:
>
> >An iterator is a function that returns a function which maintains a
> >piece of internal state.
>
> But can you compile it down to a single increment instruction on a pointer
> (for an iterator over an array)?
*In principle*, a compiler could perform closure analysis and determine
that the code pointer for the function `next' is known, so the closure
for `next' could be represented (in the case of an array iterator) as
a block containing a pointer to the array and a pointer to a reference
cell containing the current index. The code for the function could be
inlined and would consist in fetching both pieces of information, reading
the array and updating the reference cell.
*In principle*, a compiler could perform escape analysis and allocate the
reference cell on the stack, so accessing and updating it would be cheaper.
*In principle*, a compiler could perform must-alias analysis and find out
that the address of the array is already available elsewhere, thus obviating
the need to create a closure entirely.
Some ML compilers perform some of these optimizations. O'Caml performs none,
as far as I know; they are tricky to implement, especially in combination.
I'd be curious to see how C++ achieves this.
> Also, can you compare two iterators for equality?
What is the semantics of such a comparison?
--
François Pottier
Francois.Pottier@inria.fr
http://pauillac.inria.fr/~fpottier/
-------------------
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:[~2002-07-08 9:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 2:49 [Caml-list] " Oleg
2002-07-03 8:37 ` [Caml-list] " Ketanu
2002-07-03 17:29 ` Chris Hecker
2002-07-03 20:07 ` Oleg
2002-07-03 20:34 ` Alessandro Baretta
2002-07-04 15:33 ` John Max Skaller
[not found] ` <3D249B27.5080807@baretta.com>
[not found] ` <3D25D27B.2020005@ozemail.com.au>
2002-07-07 20:42 ` Alessandro Baretta
2002-07-08 0:59 ` John Max Skaller
2002-07-08 7:29 ` Alessandro Baretta
2002-10-15 0:10 ` Eray Ozkural
2002-07-03 21:55 ` Peter Wood
2002-07-04 2:02 ` james woodyatt
2002-07-04 15:18 ` John Max Skaller
2002-07-05 8:42 ` Francois Pottier
2002-07-05 9:25 ` Xavier Leroy
2002-07-05 9:57 ` Chris Hecker
2002-07-05 13:54 ` Xavier Leroy
2002-07-05 17:59 ` Chris Hecker
2002-07-05 20:31 ` John Max Skaller
2002-07-05 19:33 ` John Max Skaller
2002-07-05 19:31 ` John Max Skaller
2002-07-05 8:33 ` Francois Pottier
2002-07-05 23:05 ` Dave Berry
2002-07-08 9:54 ` Francois Pottier [this message]
2002-07-08 15:49 ` John Max Skaller
2002-08-02 14:49 ` [Caml-list] Streams Diego Olivier Fernandez Pons
2002-08-02 15:29 ` Alain Frisch
2002-08-03 14:19 ` Diego Olivier Fernandez Pons
2002-07-03 8:42 ` [Caml-list] generic programming Johan Baltié
[not found] ` <002301c22270$fb4ca160$2be213c3@youngkouzdra>
[not found] ` <20020703092753.M39371@wanadoo.fr>
2002-07-05 10:38 ` Anton Moscal
2002-07-03 9:10 ` Jun P.FURUSE
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=20020708115453.A32472@pauillac.inria.fr \
--to=francois.pottier@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