From: "Max Powers" <max_powers280@hotmail.com>
To: skaller@users.sourceforge.net
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Calling Ocaml from Python
Date: Thu, 29 Apr 2004 17:12:41 +0930 [thread overview]
Message-ID: <BAY9-F5ClbjCLP5VvfO00015697@hotmail.com> (raw)
On Thu, 2004-04-29 at 16:56, skaller wrote:
>On Thu, 2004-04-29 at 15:58, Max Powers wrote:
>
> > So as I see it I've got the following options:
> > 1) write the parser in ocaml. Wrap ocaml in C then wrap that using SWIG
>into
> > a python module.
> > 2) write the parser in C. Use SWIG to generate Ocaml and python modules.
> > 3) write the parser in python. Use Pycaml to call the python module from
> > Ocaml.
>
>Ocaml is well suited to parsing and analysing
>the parsed terms. If you head for (2) or (3) one needs
>to ask why bother using Ocaml at all?
Ah, that's 'cause I've got a huge application written (by others, I'm just
the GUI bunny) in Ocaml. They're not real happy with the current parser
(it's kind of crufty I believe), so would be happy to replace it, so long as
the data is available in the Ocaml world. Parsing config files isn't the
apps main job :).
-Max
_________________________________________________________________
Personalise your phone with chart ringtones and polyphonics. Go to
http://ringtones.com.au/ninemsn/control?page=/ninemsn/main.jsp
-------------------
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
next reply other threads:[~2004-04-29 7:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 7:42 Max Powers [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-30 1:13 Max Powers
2004-04-29 5:58 Max Powers
2004-04-29 6:56 ` skaller
2004-04-29 21:24 ` art yerkes
2004-04-29 5:07 Max Powers
2004-04-29 5:33 ` skaller
2004-04-29 3:09 Max Powers
2004-04-29 3:49 ` skaller
2004-04-29 5:45 ` Basile STARYNKEVITCH
2004-04-29 14:16 ` John Goerzen
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=BAY9-F5ClbjCLP5VvfO00015697@hotmail.com \
--to=max_powers280@hotmail.com \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
/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