From: rixed@happyleptic.org
To: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Inspect and dump values on the OCaml heap
Date: Thu, 15 Apr 2010 07:31:10 +0200 [thread overview]
Message-ID: <20100415053110.GC2321@yeeloong> (raw)
In-Reply-To: <n2tf02e7f931004141909rce52bc29i29786b88c8ba8689@mail.gmail.com>
> I am convinced that such things have *no* usefulness. If you
> are trying to debug your data structure, state its global
> invariants, prove (at whatever level of formality you are most
> comfortable with) that all API functions preserve the invariants,
> and use the module system to hide functions that do not
> preserve them. You will be done faster than trying to make
> sense of graphs and your code will be better.
Visualizing data structures does no prevent you from proving some
invariant and can give some other kind of informations, like spotting
unexpected (ir)regularities, wrong proofs, etc... Why oppose both ?
next prev parent reply other threads:[~2010-04-15 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 15:02 Kaspar Rohrer
2010-04-14 22:45 ` [Caml-list] " Richard Jones
2010-04-14 23:23 ` Kaspar Rohrer
2010-04-15 0:40 ` Martin Jambon
2010-04-15 5:19 ` rixed
2010-04-15 2:09 ` Kaustuv Chaudhuri
2010-04-15 5:31 ` rixed [this message]
2010-04-15 5:42 ` Martin Jambon
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=20100415053110.GC2321@yeeloong \
--to=rixed@happyleptic.org \
--cc=caml-list@yquem.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).