From: skaller <skaller@users.sourceforge.net>
To: Alex Baretta <alex@barettadeit.com>
Cc: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Ocaml automation update
Date: 05 Sep 2004 02:17:23 +1000 [thread overview]
Message-ID: <1094314643.3352.342.camel@pelican.wigram> (raw)
In-Reply-To: <4139E101.8040306@barettadeit.com>
On Sun, 2004-09-05 at 01:36, Alex Baretta wrote:
> I wish to let you know that the first application of ocaml to realtime
> industrial control has succeeded.
Nice job! Now we all want to know -- how did the
Ocaml GC stand up? How did you tweak it? :)
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
-------------------
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
next prev parent reply other threads:[~2004-09-04 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 15:36 Alex Baretta
2004-09-04 16:17 ` skaller [this message]
2004-09-19 18:19 ` Alex Baretta
2004-09-19 21:26 ` I R T
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=1094314643.3352.342.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=alex@barettadeit.com \
--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;
as well as URLs for NNTP newsgroup(s).