From: Malcolm Matalka <mmatalka@gmail.com>
To: John Whitington <john@coherentgraphics.co.uk>
Cc: "caml-list\@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Do you use a debugger with OCaml? If not, why not?
Date: Thu, 26 Nov 2015 10:11:35 +0000 [thread overview]
Message-ID: <86k2p5nk88.fsf@gmail.com> (raw)
In-Reply-To: <5655AE66.6000307@coherentgraphics.co.uk> (John Whitington's message of "Wed, 25 Nov 2015 12:49:42 +0000")
John Whitington <john@coherentgraphics.co.uk> writes:
> Hi,
>
> Like, I suspect, many people, my method has always been to insert Printfs, and stare at code until I find the problem. In fact, the
> ocaml.org page on ocamldebug says:
>
> "In fact, for complex programs, it is likely the case that the programmer will use explicit printing to find the bugs, since this
> methodology allows the reduction of the trace material: only useful data are printed and special purpose formats are more suited to get the
> relevant information, than what can be output automatically by the generic pretty-printer used by the trace mechanism."
>
> So, I ask: What do you use for debugging small and large OCaml programs? If not a debugger, why not? What problems prevent it? How does your
> debugging process differ when writing OCaml compared with other
> languages you use?
I do not use a debugger, but I think it's mostly due to ignorance. I
just don't know how to use a debugger effectively in any language.
That being said, I write a lot of asynchronous code which I have found
difficult to use a debugger in pretty much any language other than
Erlang.
Also, if something weird is happening in an place I don't expect, I
often try to hoist that up to the type system which can, with
discipline, inform me of when I was forgetting to handle a situation.
>
> John
>
> --
> John Whitington
> Director, Coherent Graphics Ltd
> http://www.coherentpdf.com/
next prev parent reply other threads:[~2015-11-26 10:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 12:49 John Whitington
2015-11-25 13:12 ` Francois Berenger
2015-11-25 13:23 ` Ivan Gotovchits
2015-11-25 15:27 ` Gerd Stolpmann
2015-11-25 16:04 ` Chan Ngo
2015-11-25 13:26 ` Matthieu Dubuget
2015-12-01 12:06 ` Matthieu Dubuget
2015-11-25 14:02 ` Markus Weißmann
2015-11-25 14:05 ` Nils Becker
2015-11-25 15:55 ` Daniel Bünzli
2015-11-26 9:14 ` Leonardo Laguna Ruiz
2015-11-26 10:59 ` Tom Ridge
2015-11-30 17:56 ` Xavier Van de Woestyne
2015-11-25 16:06 ` Maverick Woo
2015-11-25 16:16 ` Anton Bachin
2015-11-25 16:52 ` Michael Grünewald
2015-11-25 18:23 ` Török Edwin
2015-11-25 20:23 ` David MENTRÉ
2015-11-26 10:11 ` Malcolm Matalka [this message]
2015-11-26 10:57 ` Romain Bardou
2015-12-11 18:58 ` Richard W.M. Jones
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=86k2p5nk88.fsf@gmail.com \
--to=mmatalka@gmail.com \
--cc=caml-list@inria.fr \
--cc=john@coherentgraphics.co.uk \
/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