caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "CUOQ Pascal" <Pascal.CUOQ@cea.fr>
To: <caml-list@yquem.inria.fr>
Subject: Re: Ocaml porting issue?
Date: Fri, 22 May 2009 22:03:23 +0200	[thread overview]
Message-ID: <5EFD4D7AC6265F4D9D3A849CEA9219191AB1C3@LAXA.intra.cea.fr> (raw)
In-Reply-To: <20090522100003.F3295BC54@yquem.inria.fr>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

Hi!

Minhyuk, Kwon wrote:
> it's really hard to maintain this analyzer, so we hope change major 
> programming language by ocaml. 
> but our client's programming environment is very variant(eg. UNIX-AIX, 
> WINCE-ARM...). they only have a C compiler(gcc, aix c, etc.) 
> is there any portable issues in ocaml? this is really important thing, 
> we considered.

In short, bytecode compilation of OCaml works for every platform
for which there is a C compiler. So unless you expect speed
of your application to be a problem, you will always have the
solution of using the bytecode compiler as a back-up.

The platforms you mention as examples are a little too
exotic to completely avoid problems with the native compiler.
The majority of them will be supported, but you have to expect
that you'll be the first one to run into problems for the most
exotic ones.

I cannot resist making a last remark that is only slightly off-topic:
if the target language for your analyzer is C, it may be a good
idea to take advantage of the rewrite to make it a Frama-C
plug-in. Please find details at http://frama-c.cea.fr/

Pascal


[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3157 bytes --]

           reply	other threads:[~2009-05-22 20:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20090522100003.F3295BC54@yquem.inria.fr>]

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=5EFD4D7AC6265F4D9D3A849CEA9219191AB1C3@LAXA.intra.cea.fr \
    --to=pascal.cuoq@cea.fr \
    --cc=caml-list@yquem.inria.fr \
    /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).