Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Miles Egan <cullenx@earthlink.net>
To: caml-list@inria.fr
Subject: Looking for a nail
Date: Sun, 24 Jan 1999 15:06:05 -0600	[thread overview]
Message-ID: <99012415253804.01196@maya> (raw)

I've been working with OCaml on my own for the past two weeks or so and
think I'm finally ready to take on a real project.  I feel like I've just come
upon a beautiful new hammer and I want to find some nails to hit with it.

I'd like to work on something that might help raise OCaml's visibility among
the Linux hacker community.  A few projects have occurred to me already:

1.  Extend OCaml's Unix library.  What's already there is very useful, but
there are quite a few functions missing.  I'd be happy to help fill this out,
although I'm new enough to OCaml and functional programming that I'm still not
sure if some Unix functions were omitted because of their stateful semantics.

2.  Build a GTK+ wrapper.  I know there was some discussion of this earlier. 
Is anyone still working on this?  I think a robust, comprehensive GTK+
interface would make OCaml a stronger candidate for a lot of burgeoning
open-source projects.  Again, I'm new enough to this that I'm still not sure if
languages like OCaml are a good fit for GUI work, but it seems to me that
OCaml's mix of imperative and functional features should provide enough
flexibility for something like this.

3.  Rewrite some of the GNU build tools, autoconf, automake etc. in OCaml.  It
seems to me that OCaml would be a marvelous language for building these kinds
of tools; their current m4 / perl implementation seems inelegant to me.  On the
other hand, the FSF seems to favor scheme, so they may not be receptive to
OCaml implementations ( I haven't asked ).

I'd appreciate any criticisms of these projects or any suggestions for others. 
My goal is to do my small part to promote OCaml ( while having fun hacking
with it ) and to try to show the open-source community what a boon a tool like
OCaml can be.  With a bit of luck, maybe one day I can earn a living writing
OCaml instead of C++. :)

--
miles




             reply	other threads:[~1999-01-24 21:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-24 21:06 Miles Egan [this message]
1999-01-24 23:01 ` Lyn A Headley
1999-01-25  8:44   ` Jean-Christophe Filliatre
1999-01-25 20:45     ` Markus Mottl
1999-01-25 13:36   ` mattwb
1999-01-25 20:48     ` Trevor Jim
1999-01-25 21:57   ` Gerd Stolpmann
1999-01-25 12:45 ` Michel Schinz
1999-01-25 20:37   ` Markus Mottl
1999-01-28  9:54     ` Michel Schinz
1999-01-28 14:13       ` Markus Mottl
1999-01-25 20:53 Hendrik Tews
1999-01-26 19:20 ` Ian T Zimmerman
1999-01-28  1:30   ` John Prevost
1999-01-28 20:10   ` Hendrik Tews
1999-01-27  1:29 ` Jacques GARRIGUE
1999-01-27  8:27 ` Jean-Christophe Filliatre
1999-01-28  9:34 ` Cuihtlauac ALVARADO
1999-01-28 13:32 Don Syme
1999-01-29  0:25 ` Markus Mottl
1999-01-31 18:43 ` John Whitley
1999-01-29  0:45 Frank A. Christoph

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=99012415253804.01196@maya \
    --to=cullenx@earthlink.net \
    --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