From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Ravi Chamarty <ravi@ittc.ukans.edu>, caml-list@inria.fr
Subject: Re: Porting OCaml to A Custom OS
Date: Mon, 10 Jan 2000 14:14:03 +0100 [thread overview]
Message-ID: <20000110141402.64185@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.LNX.4.10.10001081812500.3538-100000@george.ittc.ukans.edu>; from Ravi Chamarty on Sat, Jan 08, 2000 at 06:22:33PM -0600
> Hi,
> I am trying to port OCaml to a custom operating system which is tailored
> to my needs. I wish to know what things to be taken care of. I would be
> specifically interested to know which parts of the code I may be required
> to modify?
> What are the interfaces OCaml uses to talk with the OS ?
The core runtime system uses essentially ANSI C plus a little bit of POSIX
(file descriptors, open/read/write/lseek/close). In particular, all
memory is allocated using malloc().
Some of the external libraries are more OS-dependent. For instance,
the "Unix" library relies heavily on POSIX, although a partial port to
Win32 is also available.
If you have more specific questions, feel free to ask us (caml@inria.fr)
directly.
- Xavier Leroy
next prev parent reply other threads:[~2000-01-10 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-24 10:12 OCaml makefile template comments David Mentré
1999-11-24 20:49 ` Markus Mottl
1999-11-25 12:38 ` Recursive Makefile (was: Re: OCaml makefile template comments) David Mentré
2000-01-09 0:22 ` Porting OCaml to A Custom OS Ravi Chamarty
2000-01-10 13:14 ` Xavier Leroy [this message]
[not found] <Pine.LNX.4.10.10002231549560.5472-100000@george.ittc.ukans.edu>
2000-02-25 14:05 ` Porting OCaml to a " Xavier Leroy
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=20000110141402.64185@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=ravi@ittc.ukans.edu \
/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).