From: Brian Rogoff <bpr@best.com>
To: "Krishnaswami, Neel" <neelk@cswcasa.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] A G'Caml question" + additional info
Date: Wed, 11 Jul 2001 15:47:27 -0700 (PDT) [thread overview]
Message-ID: <Pine.BSF.4.21.0107111531550.7564-100000@shell5.ba.best.com> (raw)
In-Reply-To: <B1E4D3274D57D411BE8400D0B783FF322E8656@exchange1.cswv.com>
On Wed, 11 Jul 2001, Krishnaswami, Neel wrote:
> Markus Mottl [mailto:markus@mail4.ai.univie.ac.at] writes:
> > On Wed, 11 Jul 2001, Bruce Hoult wrote:
> > > But the language itself seems to be starting to rival C++ for sheer
> > > complexity. When you want to do something you seem to have a choice
> > > of using this feature, or *this* one, or *this* newly developed one.
> >
> > Having choices is not necessarily bad, being forced to using many
> > alternatives is. I think that OCaml has succeeded quite well so far in
> > keeping different features apart as one can see in the standard library,
> > which can be used with the core language + modules alone. I hope this
> > will stay so!
>
> Permit me to disagree. I find nearly all of OCaml's features highly
> useful and orthogonal, and I am only working on medium size projects.
Good point, I was going to disagree with Bruce on the C++ comparison.
OCaml is still orthogonal, with the major exception being the overlap
between the object system and the module system. I guess that's still
research.
> For instance, I recently wrote yet another set implementation, because
> the functorial interface to the Set module in the standard library
> wouldn't let me use it in a fully polymorphic fashion. If the Set
> library had been written using OCaml's object system, then I would
> not have had to redo my own. From this experience I conclude that the
> right thing is to use the features that offer the nicest degree of
> modularity and reusability.
That's odd. If the Set library had been implemented using the object
system, it seems that you would have less (parametric) polymorphism
since OCaml doesn't (yet?) have polymorphic methods.
But, I agree that there should be polymorphic versions of some of the
functorial libraries. There is no way to directly have a recursive
type definition/functor instantiation, so if you want to implement what
OOers call the Component pattern you have to use the parameterization
trick which requires a polymorphic functor. This has bit me a few times
already. This is pretty high on my "I sure hope this gets fixed one day"
list.
BTW, if you really like OO style libraries, point your browser this-a-way
http://wwwfun.kurims.kyoto-u.ac.jp/soft/olabl/classes/
-- Brian
-------------------
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
next prev parent reply other threads:[~2001-07-11 22:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 22:23 Krishnaswami, Neel
2001-07-11 22:47 ` Brian Rogoff [this message]
2001-07-12 9:37 ` Markus Mottl
2001-07-14 2:04 ` John Max Skaller
2001-07-14 3:00 ` Alexander V. Voinov
2001-07-14 15:00 ` John Max Skaller
2001-07-11 23:10 Krishnaswami, Neel
2001-07-12 0:08 ` Brian Rogoff
2001-07-12 21:30 Krishnaswami, Neel
2001-07-13 9:34 ` Markus Mottl
2001-07-13 13:12 Krishnaswami, Neel
2001-07-13 13:35 ` Markus Mottl
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=Pine.BSF.4.21.0107111531550.7564-100000@shell5.ba.best.com \
--to=bpr@best.com \
--cc=caml-list@inria.fr \
--cc=neelk@cswcasa.com \
/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