From: Brian Hurt <bhurt@spnz.org>
To: skaller <skaller@users.sourceforge.net>
Cc: Florian Weimer <fw@deneb.enyo.de>, caml-list <caml-list@inria.fr>
Subject: Re: Ant: [Caml-list] The "Objective" part of Objective Caml
Date: Mon, 7 Nov 2005 20:15:31 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.63.0511072006270.20621@localhost.localdomain> (raw)
In-Reply-To: <1131414473.23991.37.camel@rosella>
On Tue, 8 Nov 2005, skaller wrote:
>>> The object oriented part of OCaml is roughly speaking
>>> just as capable as that of Python, C++, Java, C# etc.
>>
>> Sure, I don't doubt that.
>
> I do. The Python system is much more 'capable' and much less 'robust'.
> This is typical for dynamic typing vs static typing.
I think I'm with Skaller here- Objects in Ocaml are much less powerfull
than they are in (for example) Java or Python. For example, objects in
Ocaml can not have non-virtual (non-overloadable) methods, or static
(global) methods. So patterns like singletons are hard to implement with
Ocaml objects.
But that's OK- because Ocaml provides other ways to provide those
capabilities. The problem I have with a lot of pure-OO languages is the
need to make objects do everything. The proper way to do a singleton in
Ocaml is to use modules, not objects. If you're not using the true power
of objects- inheritance, virtual functions, and overloading- you shouldn't
be using objects. So the fact that Ocaml doesn't provide support for
these non-objects isn't a problem.
Brian
next prev parent reply other threads:[~2005-11-08 2:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 22:45 Florian Weimer
2005-11-07 21:41 ` Ant: [Caml-list] " Martin Chabr
2005-11-07 21:55 ` Florian Weimer
2005-11-08 1:47 ` skaller
2005-11-08 2:15 ` Brian Hurt [this message]
2005-11-08 7:15 ` Daniel Bünzli
2005-11-08 15:02 ` Brian Hurt
2005-11-08 15:39 ` Alexander Fuchs
2005-11-08 15:42 ` Matt Gushee
2005-11-08 15:56 ` Michael Wohlwend
2005-11-08 18:16 ` brogoff
2005-11-08 22:04 ` Brian Hurt
2005-11-08 23:40 ` brogoff
2005-11-09 9:00 ` skaller
2005-11-11 15:28 ` Florian Weimer
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.LNX.4.63.0511072006270.20621@localhost.localdomain \
--to=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=fw@deneb.enyo.de \
--cc=skaller@users.sourceforge.net \
/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