From: Adam Scislowicz <kor@koure.dyn.ml.org>
To: caml-list@inria.fr
Subject: Wish List / Future direction?
Date: Tue, 16 Dec 1997 22:01:24 -0500 [thread overview]
Message-ID: <97121622191200.14743@koure.dyn.ml.org> (raw)
Near Future Wishes:
1) independent of ANY external library (libc libm libncurses for example)
2) reflectivity support :/
3) dynamic linking of native modules
4) NASM output as an option at first, but when NASM adds multiplatform support
it should be used instead of as, this would allow the use of OCAML/NASM without
the bloat of gcc/gdb/binutils/glibc.
Small changes:
1) optimization of recursive functions.
WHY?
I would like to implement an efficient exokernel, and I also would like the base system to
use as little space as possible. Though without a C library much would have to be rewritten
we cant keep old things around forever :(...
I will patch emit.mlp for x86 NASM, and eventually Alpha and StrongARM NASM. I will also
of course add patches for my object file format, but I cannot implement reflectivity, and
I was wondering if you planned on it any time soon?
-Adam Scislowicz(kor@earthling.net)
(core@x2.alliance.net)
Thank you for implementing such a powerfull development system :)
reply other threads:[~1997-12-17 18:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=97121622191200.14743@koure.dyn.ml.org \
--to=kor@koure.dyn.ml.org \
--cc=caml-list@inria.fr \
--cc=kor@earthling.net \
/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).