From: Tom <tom7ca@yahoo.com>
To: Eric Newhuis <enew@starband.net>, caml-list@inria.fr
Subject: Re: [Caml-list] Rewriting UNIX in Caml and getting rid of the C disease
Date: Sun, 11 Nov 2001 00:22:13 -0800 (PST) [thread overview]
Message-ID: <20011111082213.51037.qmail@web11901.mail.yahoo.com> (raw)
In-Reply-To: <003401c16a77$aa5f2860$0401a8c0@XENO>
There are is probably a lot more non-C/C++, safe software in Linux and
UNIX than in Windows NT. Linux and UNIX use shell, Perl, Python, and
awk extensively--safe, high-level programming languages (if dynamically
typed). Linux installations often also use cfengine, a kind of expert
system shell for system configuration. And this is nothing new: 15 years
ago, statistics at Bell Labs showed that people spent a lot more compute
cycles in awk than in native C programs.
Still, dynamic languages have their limitations, and it would be
nice to rethink and build larger parts of the Linux
environment in ML, in part to achieve more safety, and in part to make
it easier to modify and extend system software. Both UNIX and ML
would benefit from the experience and results. Utilities
like "unison" and "bibtex2html" (both written in OCAML)
are a good indication that ML can be used for such applications.
I think most people don't spend much time on it because there isn't
really a big itch that needs to be scratched for them. Apache, or "GNU
ls", may both be messy, hard-to-maintain C programs, but they get the
job done and someone else is doing the testing, so why bother
rewriting them? Still, all it takes is volunteers, so go ahead
and pick a project.
Tom
--- Eric Newhuis <enew@bigfoot.com> wrote:
> <seriousness>
> Is there a market for such a thing? Defense? Secure operating systems?
> What are all the tangible benefits?
> </seriousness>
>
> <humor>
> What will the name fo the OS be? SafeLix? FreeBSafeD?
> </humor>
>
> <opinion>
> Windows NT might already be part of the way there depending on how one views
> Prolog as being closer to Caml. I guess they're both functional. Has
> Prolog, used in the following manner, added the safety you hope to achieve?
> And could Caml have also achieved it?
> </opinion>
>
> <fact>
> Microsoft used Prolog in NT's network stack.
> http://research.microsoft.com/research/dtg/davidhov/pap.htm
> </fact>
>
> -------------------
> Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ:
> http://caml.inria.fr/FAQ/
> To unsubscribe, mail caml-list-request@inria.fr Archives:
http://caml.inria.fr
__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-11-11 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 5:17 Berke Durak
2001-11-11 6:11 ` Eric Newhuis
2001-11-11 8:22 ` Tom [this message]
2001-11-11 12:47 ` Sven
2001-11-11 13:32 ` Julian Assange
2001-11-12 8:32 ` Jeff Henrikson
2001-11-12 13:39 ` Mark Seaborn
2001-11-12 17:33 ` [Caml-list] GCCXML: don't write your own C parser. (WAS: Rewriting UNIX . . .) Jeff Henrikson
2001-11-13 0:53 ` Berke Durak
2001-11-13 5:10 ` Julian Assange
2001-11-12 21:52 [Caml-list] Rewriting UNIX in Caml and getting rid of the C disease Arturo Borquez
2001-11-21 21:25 Michael Hicks
2001-11-22 3:10 ` Rafael 'Dido' Sevilla
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=20011111082213.51037.qmail@web11901.mail.yahoo.com \
--to=tom7ca@yahoo.com \
--cc=caml-list@inria.fr \
--cc=enew@starband.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