From: Ravi Chamarty <ravi@ittc.ukans.edu>
To: caml-list@inria.fr
Subject: Porting OCaml to A Custom OS
Date: Sat, 8 Jan 2000 18:22:33 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.10.10001081812500.3538-100000@george.ittc.ukans.edu> (raw)
In-Reply-To: <wd8ogckqjuw.fsf@parate.irisa.fr>
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 ?
Thanks,
Ravi
----------------------------------------------------------
Ravi S Chamarty E-mail: ravi@ittc.ukans.edu
Graduate Research Assistant, Voice :785-864-7799
ITTC,2291 Irving Hill Road,
University of Kansas,
Lawrence KS 66044-7541
next prev parent reply other threads:[~2000-01-10 8:49 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 ` Ravi Chamarty [this message]
2000-01-10 13:14 ` Porting OCaml to A Custom OS Xavier Leroy
[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=Pine.LNX.4.10.10001081812500.3538-100000@george.ittc.ukans.edu \
--to=ravi@ittc.ukans.edu \
--cc=caml-list@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