From: "Nicolas Cannasse" <warplayer@free.fr>
To: "Richard Jones" <rich@annexia.org>
Cc: "caml-list" <caml-list@pauillac.inria.fr>
Subject: Re: [Caml-list] laziness
Date: Mon, 6 Sep 2004 08:11:42 +0200 [thread overview]
Message-ID: <002101c493d8$61a6b1f0$19b0e152@warp> (raw)
In-Reply-To: <20040906005741.GA20406@annexia.org>
> Doesn't laziness often indicate a bug in the code? ie. You've
> written an expression in the program, but that expression is never
> used. This is dead code, right? Hence a bug?
Laziness can be useful in some cases (eg : enums in ExtLib) and I use it for
example in a typing algorithm where you need to duplicate big objects type
for unification but you're not sure in advance which field(s) will be
unified, so you delay it when they get accessed. It's kind of internet
browser cache.
Evaluated part of a program can depends on several kind of inputs, and is
undecidable. Then you cannot make automated assertion about what part will
never be evaluated in the general case (although this can be done in
specific cases). However what you can do is automated flow analysis to check
which part of your program are not accessible through some entry points :
this is interesting for dead code removal and test coverage but can be
tricky to do in OCaml.
Regards,
Nicolas Cannasse
-------------------
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-06 6:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 1:07 Jason Smith
2004-09-05 5:46 ` skaller
2004-09-06 0:57 ` Richard Jones
2004-09-06 6:11 ` Nicolas Cannasse [this message]
2004-09-06 8:24 ` skaller
2004-09-06 8:44 ` Erik de Castro Lopo
2004-09-06 12:55 ` Jon Harrop
2004-09-06 16:21 ` William Lovas
2004-09-06 22:35 ` Hartmann Schaffer
2004-09-07 8:31 ` Richard Jones
2004-09-07 8:37 ` Nicolas Cannasse
-- strict thread matches above, loose matches on Subject: below --
2004-09-06 12:17 Jason Smith
2004-09-06 17:00 ` skaller
2004-09-06 9:16 Jason Smith
2004-09-06 9:07 Jason Smith
2004-09-06 10:18 ` skaller
2004-09-04 6:30 skaller
2004-09-04 8:40 ` Marcin 'Qrczak' Kowalczyk
2004-09-04 11:21 ` skaller
2004-09-04 11:49 ` Richard Jones
2004-09-04 20:40 ` Hartmann Schaffer
2004-09-05 10:50 ` Jon Harrop
2004-09-05 14:07 ` 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='002101c493d8$61a6b1f0$19b0e152@warp' \
--to=warplayer@free.fr \
--cc=caml-list@pauillac.inria.fr \
--cc=rich@annexia.org \
/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).