caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mark Shinwell <Mark.Shinwell@cl.cam.ac.uk>
To: yoann padioleau <padator@wanadoo.fr>
Cc: remi.vanicat@gmail.com, caml-list@inria.fr
Subject: Re: [Caml-list] Dumping of Typedtree
Date: Thu, 15 Sep 2005 10:01:13 +0100	[thread overview]
Message-ID: <20050915090113.GG5470@three-tuns.net> (raw)
In-Reply-To: <13302554.1126721135427.JavaMail.www@wwinf1001>

On Wed, Sep 14, 2005 at 08:05:35PM +0200, yoann padioleau wrote:
> > Message du 14/09/05 19:54
> > De : "Remi Vanicat" <remi.vanicat@gmail.com>
> > A : "Mark Shinwell" <Mark.Shinwell@cl.cam.ac.uk>
> > Copie ?? : caml-list@inria.fr
> > Objet : Re: [Caml-list] Dumping of Typedtree
> > 
> > 2005/9/14, Mark Shinwell <Mark.Shinwell@cl.cam.ac.uk>:
> > > This is mainly directed at the current O'Caml maintainers.
> > > 
> > > Does there exist anywhere a piece of code for dumping the typed syntax
> > > tree representations (values of type Typedtree.structure etc) which are
> > > used inside the compiler?  I can't find anything in the compiler to do
> > > this at the moment, and it looks moderately tedious to write.
> 
> You can use the dumper module by richard jones.
>  http://merjis.com/developers/dumper
> The result is not perfect but it does a good job for fast debugging.

I already have a piece of code which does that, as it happens: the
problem is that you don't get constructor names, etc.  It needs to be
something which I can build in with the compiler sources so that this
information is preserved.

Mark


  reply	other threads:[~2005-09-15  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 18:05 yoann padioleau
2005-09-15  9:01 ` Mark Shinwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-14 14:16 Mark Shinwell
2005-09-14 17:54 ` [Caml-list] " Remi Vanicat

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=20050915090113.GG5470@three-tuns.net \
    --to=mark.shinwell@cl.cam.ac.uk \
    --cc=caml-list@inria.fr \
    --cc=padator@wanadoo.fr \
    --cc=remi.vanicat@gmail.com \
    /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).