From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Function returning recursive lists
Date: Fri, 04 Jan 2013 09:45:38 +0900 [thread overview]
Message-ID: <50E62632.4060208@riken.jp> (raw)
In-Reply-To: <CA+Lkvyrg_guvYxUCuSY01v+7FchuHeBpLKT6btJZFWMUG4xJhg@mail.gmail.com>
On 12/29/2012 12:22 AM, Didier Cassirame wrote:
> Hi all,
>
> Regarding the original question, wouldn't it be easier to implement it
> as a stream?
It smells as someone needs a stream or a lazy list indeed.
Happy new year! ;)
> didier
>
> 2012/12/28, Philippe Wang <mail@philippewang.info>:
>> On Fri, Dec 28, 2012 at 2:41 AM, Peter Frey <pjfrey@sympatico.ca> wrote:
>>
>>> The problem with docycle is not its coding style but that it produces in
>>> fact a cyclic list, which is not very useful: Almost all functions, such
>>> as List.rev are undefined.
>>
>> From my point of view, this coding style is fundamentally *wrong*:
>> - it makes assumptions on the internal data representation,
>> - and it prevents the compiler from making any optimisation from the
>> fact that elements of built-in lists are immutable (and if the
>> compilers makes some optimisations from that fact, then it's not only
>> the style but the program that is wrong).
>>
>> Cheers,
>>
>> --
>> Philippe Wang
>> mail@philippewang.info
>>
>> --
>> Caml-list mailing list. Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>
next prev parent reply other threads:[~2013-01-04 0:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 8:37 Eric Jaeger
2012-12-21 19:55 ` Peter Frey
2012-12-22 18:10 ` Philippe Wang
[not found] ` <50D59147.3000201@ssi.gouv.fr>
2012-12-28 1:41 ` Peter Frey
2012-12-28 9:37 ` Arkady Andrukonis
2012-12-28 12:21 ` Philippe Wang
2012-12-28 12:30 ` Philippe Wang
2012-12-28 15:22 ` Didier Cassirame
2013-01-04 0:45 ` Francois Berenger [this message]
[not found] <50d02b72.7155c20a.1dbf.4e2fSMTPIN_ADDED_BROKEN@mx.google.com>
2012-12-18 9:35 ` Gabriel Scherer
[not found] <50d02b65.6c4cb40a.66ab.4256SMTPIN_ADDED_BROKEN@mx.google.com>
2012-12-18 11:21 ` Julien Blond
2012-12-18 13:13 ` Eric Jaeger
[not found] ` <50d06c18.0f5cc20a.16d8.ffff8b8cSMTPIN_ADDED_BROKEN@mx.google.com>
2012-12-19 16:45 ` Lukasz Stafiniak
[not found] <50d02b62.827bc20a.6f6e.65b8SMTPIN_ADDED_BROKEN@mx.google.com>
2012-12-19 22:23 ` Philippe Wang
2012-12-19 23:50 ` Jeremy Yallop
2012-12-20 15:24 ` Ashish Agarwal
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=50E62632.4060208@riken.jp \
--to=berenger@riken.jp \
--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).