Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: konrad <konrad@mail.in.tum.de>
To: Denis Bueno <dbueno@gmail.com>
Cc: Joel Reymont <joelr1@gmail.com>, OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Testing lexers and parsers
Date: Tue, 27 Feb 2007 17:20:03 +0100	[thread overview]
Message-ID: <3780513f01438e27a484513e22b4a4fe@mail.in.tum.de> (raw)
In-Reply-To: <6dbd4d000702270811h55247a3bi808053a24ee8238d@mail.gmail.com>


I actually attended a project in university on writing a C compiler (written in Java) and we printed out XML code for debugging, that represented the AST. That was a real benefit cause you can still see the structure of the AST in the XML tree. It is even easy to do that - one tree traversal is enough.

chris

On Tue, 27 Feb 2007 11:11:09 -0500, "Denis Bueno" <dbueno@gmail.com> wrote:
> [Meant to send to the list the first time. Sorry for the dupe.]
> 
> On 2/27/07, Denis Bueno <dbueno@gmail.com> wrote:
>> On 2/27/07, Joel Reymont <joelr1@gmail.com> wrote:
>> > Are you printing out the AST to make sure you can reproduce the
>> > original file you parsed?
> 
> Yes. I wanted to make sure my AST-printing functions would print
> correct source code in the source language. This makes it very easy to
> inspect AST fragments.
> 
> -Denis
> 
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs



      reply	other threads:[~2007-02-27 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 15:29 Joel Reymont
2007-02-27 15:42 ` [Caml-list] " Denis Bueno
2007-02-27 15:46   ` Joel Reymont
     [not found]     ` <6dbd4d000702270810h16ea3308k49dfcf7e5a479ecb@mail.gmail.com>
2007-02-27 16:11       ` Denis Bueno
2007-02-27 16:20         ` konrad [this message]

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=3780513f01438e27a484513e22b4a4fe@mail.in.tum.de \
    --to=konrad@mail.in.tum.de \
    --cc=caml-list@inria.fr \
    --cc=dbueno@gmail.com \
    --cc=joelr1@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