caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Frederick Akalin <akalin@akalin.cx>
To: caml-list <caml-list@inria.fr>
Subject: ocamldebug and abstract record types
Date: Sun, 21 May 2006 00:40:20 -0700	[thread overview]
Message-ID: <B0430106-0F99-4458-BEA9-54E9EE8B23A7@akalin.cx> (raw)

At the risk of starting another flamewar, I have another question.  I  
notice that if I have a record type that's defined in an .mli file, I  
am able to print objects of that type and see its contents in the  
debugger.  However, if I make that type abstract (only defining it in  
the .ml file), I am unable to do so, instead seeing "<abstr>", unless  
I am in the .ml file where the type is defined.

Surely this information is available to the debugger from anywhere in  
the program?  Currently I make most of my types non-abstract simply  
because it is impossible to debug my programs without being able to  
check record contents, a practice which I would like to avoid having  
to do.  I am used to gdb, which prints out all a struct's contents  
regardless of protected/private modifiers, or Perl, which provides a  
similar facility with the Data::Dumper module.

I am aware that the debugger lets you load printing functions, a  
facility which I am now exploring.  Although my first impression is  
that it requires a non-trivial amount of work, both on the coding and  
debugging side.

Incidentally, how sophisticated is the debugger planned to be?  Is it  
only supposed to be used for quick-and-dirty debugging and not as a  
replacement for the toplevel?

Frederick Akalin


             reply	other threads:[~2006-05-21  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21  7:40 Frederick Akalin [this message]
2006-05-21  9:57 ` [Caml-list] " Jacques Garrigue
2006-05-22  9:05 ` Richard 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=B0430106-0F99-4458-BEA9-54E9EE8B23A7@akalin.cx \
    --to=akalin@akalin.cx \
    --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).