From: Michal Moskal <malekith@pld-linux.org>
To: "Michaël Grünewald" <michael-grunewald@wanadoo.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: uname for Ocaml
Date: Fri, 24 Jan 2003 11:36:26 +0100 [thread overview]
Message-ID: <20030124103626.GA3390@roke.freak> (raw)
In-Reply-To: <87u1g1uo66.fsf@ketanu.dyndns.org>
On Wed, Jan 22, 2003 at 05:47:29PM +0100, Michaël Grünewald wrote:
> Basile STARYNKEVITCH <basile@starynkevitch.net> writes:
>
> > Dear All,
> >
> > If you need to call uname(2) from some Ocaml program you can steal my
> > tiny code in util.ml util.mli util_ml.c on
> >
> > I actually wish that uname(2) will be incorporated in the Unix module.
>
> Would not be more accurate to complete, and much more simple, the
> 'Sys.os_type' information string by a 'Sys.os_name' information string
> (or os_uname ...).
There are also other fields in structure returned by uname:
struct utsname {
char sysname[];
char nodename[];
char release[];
char version[];
char machine[];
#ifdef _GNU_SOURCE
char domainname[];
#endif
};
I don't see much point messing with Sys modules with all this stuff.
--
: Michal Moskal ::::: malekith/at/pld-linux.org : GCS {C,UL}++++$ a? !tv
: PLD Linux ::::::: Wroclaw University, CS Dept : {E-,w}-- {b++,e}>+++ h
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2003-01-24 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 15:23 [Caml-list] " Basile STARYNKEVITCH
2003-01-21 20:29 ` Issac Trotts
2003-01-21 20:53 ` Basile STARYNKEVITCH
2003-01-21 22:42 ` Issac Trotts
2003-01-22 16:47 ` [Caml-list] " Michaël Grünewald
2003-01-24 10:36 ` Michal Moskal [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=20030124103626.GA3390@roke.freak \
--to=malekith@pld-linux.org \
--cc=caml-list@inria.fr \
--cc=michael-grunewald@wanadoo.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