From: Brian Rogoff <bpr@best.com>
To: Hao-yang Wang <hao-yang_wang@filemaker.com>
Cc: caml-list@inria.fr
Subject: [Caml-list] Re: OCaml for Windows: a suggestion
Date: Tue, 13 Feb 2001 08:25:14 -0800 (PST) [thread overview]
Message-ID: <Pine.BSF.4.21.0102130804100.1575-100000@shell5.ba.best.com> (raw)
In-Reply-To: <200102130429.UAA01798@imap.filemaker.com>
On Mon, 12 Feb 2001, Hao-yang Wang wrote:
> I don't mind whether the development environment of ocaml itself is built
> with MSVC or gcc. However, the interoperatibility (spelling?) between
> codes written in ocaml and MSVC is important to me.
Having been in that world, I agree, if you're doing professional work you
want to pay all the $$ for the full MS developers kit and have Ocaml
working with that.
This is actually where a Consortium is helpful. Maintaining the port is
actually "engineering effort" (no pejorative intended) and if the
companies making big $$ in that big market kick in the money you can hire
an engineer full time to keep the port going, getting back ends for the
.NET VM, low level bindings to Windows libraries, etc. Not my interest,
but it's not helping competitors and allows INRIA to use their time to
help us all.
-- Brian
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-02-13 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 4:36 Hao-yang Wang
2001-02-13 16:25 ` Brian Rogoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-14 17:50 [Caml-list] " Dave Berry
2001-02-12 21:27 Lionel Fourquaux
2001-02-14 15:32 ` [Caml-list] " Vijay Chakravarthy
2001-02-13 18:07 ` Mattias Waldau
2001-02-13 18:20 ` Gerd Stolpmann
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=Pine.BSF.4.21.0102130804100.1575-100000@shell5.ba.best.com \
--to=bpr@best.com \
--cc=caml-list@inria.fr \
--cc=hao-yang_wang@filemaker.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).