caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Pierre Weis <pierre.weis@inria.fr>
To: josh@trdlnk.com (Josh Smith)
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Camlp4 help/questions
Date: Wed, 28 Jul 2004 10:03:45 +0200 (MET DST)	[thread overview]
Message-ID: <200407280803.KAA01930@pauillac.inria.fr> (raw)
In-Reply-To: <20040727214504.GA7950@trdlnk.com> from Josh Smith at "Jul 27, 104 04:45:04 pm"

> I apologize if this is not the right list to send this too, but I'm 
> nearing my feeble wits' end and I'm starting here...
> 
> I have a project that is currently using c++ that I would like to convert to
> Ocaml (parts of it are already in Ocaml and I'd like to simplify my
> codebase). However, I am using the Spirit library from Boost to do parsing
> in c++ and I cannot figure out Camlp4 to convert it.  If there is anyone who
> knows both Spirit and Camlp4 who can help me I was appreciate it a lot.
> 
> Maybe I am an idiot, but I've been through the tutorial and it didn't help
> me very much. I've been looking for example code for simple parsers and I've
> found many, many calculators but little else. I've even tried to go back to 
> ocamlyacc/ocamllex but the yacc/lex syntax bothers me.
> 
> I can even give you an example of what I'm trying to parse and then use the
> resulting data structure (I could do regex, but these are from largish data
> files and the robostness provided by a parser is what I need).
> 
> a23fassssadfj4532|10,2;13,3;20;20|10|20|30|B
> aassafjeifdfj4532|11,21;13,33|1|2|3|T
> ... and so on for about a million lines or so
> 
> the unasked question here is "Is this the right way to go?" I mean, is
> Camlp4 the tool I should be using?  I think it is, because the top down,
> recursive descent parsing is what Spirit does, but maybe I've just confused
> things.  
> 
> Any help is appreciated.  Thank you all.
> 
> -jbs

If you need not parsing more complex things, you may also try the
Scanf module which is far more powerful than the C equivalent and
sounds the more appropriate for such kind of job.

I would be glad to help if you choose that way.

Best regards,

Pierre Weis

INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis/


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      parent reply	other threads:[~2004-07-28  8:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-25  8:17 [Caml-list] Map + Set Martin Jambon
2004-07-25 16:26 ` Matt Gushee
2004-07-25 17:01 ` Brian Hurt
2004-07-26 10:40   ` Matthieu Sozeau
2004-07-26 15:25     ` Brian Hurt
2004-07-26 15:47       ` Martin Jambon
2004-07-26 16:26         ` Brian Hurt
2004-07-26  7:43 ` Diego Olivier Fernandez Pons
2004-07-26 16:24   ` Martin Jambon
2004-07-26 16:52     ` Diego Olivier Fernandez Pons
2004-07-27 21:45   ` [Caml-list] Camlp4 help/questions Josh Smith
2004-07-27 22:11     ` Brian Hurt
2004-07-28  1:15       ` Josh Smith
     [not found]     ` <200407272307.50167.jon@jdh30.plus.com>
2004-07-28  1:38       ` Josh Smith
2004-07-28  8:03     ` Pierre Weis [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=200407280803.KAA01930@pauillac.inria.fr \
    --to=pierre.weis@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=josh@trdlnk.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).