caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Krishnaswami, Neel" <neelk@cswcasa.com>
To: "'caml-list@inria.fr'" <caml-list@inria.fr>
Subject: [Caml-list] Re: Debuggers (was Jihad)
Date: Wed, 7 Nov 2001 14:19:17 -0500	[thread overview]
Message-ID: <B1E4D3274D57D411BE8400D0B783FF32A8D590@exchange1.cswv.com> (raw)

Bauer, Robert [mailto:rbauer@rational.com] wrote:
>
> Case in point - debugging; one advantage of the imperative paradigm 
> is that being based on turing machines, it provides (indeed requires)
> explicit notions of state - this makes debugging easier - the ocaml 
> debugger is not very modern with respect debuggers for imperative
> languages  - even though it is leaps and bounds better than anything
> available for say, haskell.

I agree with some of the specific details in support of this claim, 
but disagree with the claim itself. Ocaml's debugger is in one respect
extremely advanced: it is a reversible debugger, which puts it way ahead
of most languages' debuggers, imperative or not. It is in one other 
respect inferior to common debuggers: you can't set conditional 
breakpoints (aka watchpoints) in it.

I don't think that this is due to any intrinsic problem caused by 
Caml's functional nature, though. After all, Smalltalk and Lisp are 
famous for providing the ultimate in debugging environments, and 
both of them have higher-order functions and offer the debugger 
vastly less in the way of reliable type constraints than Caml does.

I think (as confidently as I can without reading the source :) that it 
would be relatively straightforward to add that to camldebug. However, 
I won't add it mostly because I don't use debuggers when I have an
interactive prompt available (such as the ocaml program provides), 
because with a toplevel it's easier to write small functions, test 
them right there, and compose them incrementally.


--
Neel Krishnaswami
neelk@cswcasa.com
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


             reply	other threads:[~2001-11-07 19:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07 19:19 Krishnaswami, Neel [this message]
2001-11-07 19:51 ` [Caml-list] Re: Debuggers Eric Newhuis
2001-11-07 20:12 ` [Caml-list] debugger backtracking/checkpoints Chris Hecker
2001-11-07 20:29   ` Pixel
2001-11-08 15:14   ` Thorsten Ohl
2001-11-08 18:04     ` Christophe Raffalli
2001-11-09  9:51       ` Jerome Vouillon
2001-11-10 13:39   ` Mattias Waldau
2001-11-10 14:41     ` Dmitry Bely
2001-11-12 18:37     ` Chris Hecker

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=B1E4D3274D57D411BE8400D0B783FF32A8D590@exchange1.cswv.com \
    --to=neelk@cswcasa.com \
    --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).