caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Fritz Wuehler <fritz@spamexpire-200406.rodent.frell.eu.org>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: Efficient C++ Interfacing?
Date: 09 Jun 2004 05:13:38 +1000	[thread overview]
Message-ID: <1086722017.16811.901.camel@pelican.wigram> (raw)
In-Reply-To: <3a4641a78693342be4a5f7172e068f53@remailer.frell.eu.org>

On Wed, 2004-06-09 at 01:02, Fritz Wuehler wrote:

> > I want to process data with OCaml
> 
> Oh, I thought Felix wanted to be bootstrapped.

It does, eventually. however, to do that
I would have to write some very complex
code in an unstable language (Felix).
[At the moment, Ocaml is better for writing
compilers in :]

> Since Felix is so C++ friendly it should be
> easy to drop OpenC++ in to help bootstrapping.
> Seems a waste to write a C++ parser in Ocaml
> that has to be rewritten in Felix later.

Sure but you're effectively suggesting to use
OpenC++ and which means building a representation
using C++ code.

> This thing was designed to do what Felix
> does, make (C++)++ languages.  It can also
> for example deal with Qt's non-C++ issues,
> which is just another (C++)++.

Felix isn't a (C++)++ language syntactically:
the syntax is unambiguous LALR(1) .. :)

You are right I suspect I could write the
wrapper generator in C++ instead of Ocaml,
and then leverage OpenC++ to do the
parsing. There are also several other C++ parsers
including part of CERN's ROOT system.

However this complicates the tool chain quite
a lot. The wrapper generator excluding the parser
is only a few hundred lines of code at the moment.
The C parser is a bit bigger, but I didn't write it.

-- 
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850, 
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net



-------------------
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


  reply	other threads:[~2004-06-08 19:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 15:02 Fritz Wuehler
2004-06-08 19:13 ` skaller [this message]
2004-06-08 20:49 ` Eray Ozkural
2004-06-08 21:19   ` £ukasz Dobrek
2004-06-28 19:58     ` Eray Ozkural
2004-06-29  1:35       ` skaller
2004-07-07  1:02         ` Eray Ozkural
2004-07-07  6:59           ` skaller
2004-07-07  3:29         ` Ethan Lee Aubin
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07 11:46 privacy.at Anonymous Remailer
2004-06-07 15:50 ` skaller

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=1086722017.16811.901.camel@pelican.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=fritz@spamexpire-200406.rodent.frell.eu.org \
    /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).