caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kathleen Fisher <kfisher@research.att.com>
To: caml-list@yquem.inria.fr
Cc: John Reppy <jhr@cs.uchicago.edu>
Subject: 
Date: Mon, 23 Jan 2006 11:37:14 -0800	[thread overview]
Message-ID: <D8C6F1F5-0F73-4C82-AB38-252CC17BB38D@research.att.com> (raw)

As part of our work on Moby, John Reppy and I are collecting
experiences people have had using the object-oriented features of
Ocaml, as it has been available long enough for people to use it "for
real."

We are interested in understanding what people use the object- 
oriented features for.  What works really well?  What doesn't work so  
smoothly?  How do you decide when to use the object-oriented  
features?  Do you have other observations you'd like to share?

I'm happy to summarize responses sent directly to me for the list.

Thanks in advance!
Kathleen Fisher






             reply	other threads:[~2006-01-23 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23 19:37 Kathleen Fisher [this message]
2006-01-24  6:44 ` [Caml-list] " skaller

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=D8C6F1F5-0F73-4C82-AB38-252CC17BB38D@research.att.com \
    --to=kfisher@research.att.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=jhr@cs.uchicago.edu \
    /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).