caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Mentre <David.Mentre@inria.fr>
To: "emil artin" <emil.artin@web.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml for system programming?
Date: 12 Sep 2001 10:30:21 +0200	[thread overview]
Message-ID: <qtlheu8yfoi.fsf@pochi.inria.fr> (raw)
In-Reply-To: <200109111633.f8BGXOx23823@mailgate5.cinetic.de>

"emil artin" <emil.artin@web.de> writes:

>  But I don't know if it is managable at all!!

OCaml is able to read and write bytes on a Unix file descriptor, it is
also able to handle bit operations and you have both Int32 and Int64
data types. So it should be doable. The only lacking C feature is C
struct. 

However, I'm not sure it will be easier to do those low level
manipulations in OCaml than in C.

> It would be interesting (at least for me) to know if one can do things
> like file system implementation in OCaml?

If you are thinking of doing an OCaml linux kernel module to implement a
filesystem, clearly you can't do it (mainly due to the GC that needs the
glibc malloc() and/or sbrk() and would have to work in the kernel
address space).

Now, if you are speaking of doing a pure userland filesystem tool, it
should be doable, as said above.

If you progress in this direction, I would be personnaly interested to
have your feedback on the point.

Best regards,
d.
-- 
 David.Mentre@inria.fr
 Opinions expressed here are only mine.
-------------------
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


      parent reply	other threads:[~2001-09-12  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-11 16:33 emil artin
2001-09-11 17:10 ` Benjamin C. Pierce
2001-09-11 23:02 ` SooHyoung Oh
2001-09-12  8:30 ` David Mentre [this message]

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=qtlheu8yfoi.fsf@pochi.inria.fr \
    --to=david.mentre@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=emil.artin@web.de \
    /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).