From: Eric Stokes <eric.stokes@csun.edu>
To: John Goerzen <jgoerzen@complete.org>
Cc: caml-list@inria.fr, Jere Sanisalo <xm_ocaml@xmunkki.org>
Subject: Re: [Caml-list] OCaml to C
Date: Mon, 10 May 2004 13:03:39 -0700 [thread overview]
Message-ID: <20F8ECA6-A2BD-11D8-BE86-000A95A1E69A@csun.edu> (raw)
In-Reply-To: <20040510191010.GA14068@excelhustler.com>
On May 10, 2004, at 12:10 PM, John Goerzen wrote:
> On Sun, May 09, 2004 at 11:50:00AM +0300, Jere Sanisalo wrote:
>> On Sat, May 08, 2004 at 04:37:16PM -0500, John Goerzen wrote:
>>> However, if you are going to do that, why not just compile the code
>>> to
>>> native code with ocamlopt and not worry about the C piece?
>>
>> Because ocaml compilers/runtimes do not exist for every platform (say,
>> consoles). And because compiling to C code could allow you to write
>> independent libraries for others to use. It would be nice to release
>> libraries that do a ton of stuff, usable for C/C++ coders, that were
>> written
>> easily with ocaml. And also some managers seem to trust projects that
>> are
>> "pure C/C++" much more than projects that use a variable amount of
>> languages.
>
> IMHO, a better approach than generating C output of questionable
> usefulness would be to extend ocamlopt to:
>
> 1. Support those platforms it doesn't yet;
> 2. Support output to .o/.a/.so/.dll files to directly generate
I would personally very much like to see ocamlopt able to generate
shared libraries, both for use directly with Ocaml (eg .cmxso), and
for linking with C programs.
> C-style shared libraries.
>
> I still don't see the utility of the massive undertaking that would be
> necessary to actually generate full C code from OCaml. I doubt that
> anyone would be able to maintain that C code directly in any meaningful
> way, which pretty much negates any manager-related benefit.
>
> -- John
>
> -------------------
> 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
>
-------------------
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
prev parent reply other threads:[~2004-05-10 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 21:11 Jon Harrop
2004-05-08 21:37 ` John Goerzen
2004-05-09 8:50 ` Jere Sanisalo
2004-05-09 19:48 ` David Brown
2004-05-10 19:10 ` John Goerzen
2004-05-10 20:03 ` Eric Stokes [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=20F8ECA6-A2BD-11D8-BE86-000A95A1E69A@csun.edu \
--to=eric.stokes@csun.edu \
--cc=caml-list@inria.fr \
--cc=jgoerzen@complete.org \
--cc=xm_ocaml@xmunkki.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