From: brogoff@speakeasy.net
To: Benjamin Geer <ben@socialtools.net>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] does class polymorphism need to be so complicated?
Date: Wed, 20 Aug 2003 17:58:54 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0308201743530.20778-100000@grace.speakeasy.net> (raw)
In-Reply-To: <3F43E250.1040903@socialtools.net>
On Wed, 20 Aug 2003, Benjamin Geer wrote:
> brogoff@speakeasy.net wrote:
> > If you want to solve your problem, you'll need to coerce,
> > [...]
> > A solution using polymorphic methods is sketched next,
>
> These are the two options I described in my original post. Both are
> inconvenient. My original questions remain:
Sorry, I didn't read your original post, only Brian Hurt's reply to it.
Jacques Garrigue explained the reasons why it is hard to do everything you
want in OCaml, but I still think you are being a bit harsh.
First, calling the methods through functions is not the uncontested evil that
you make it out to be.
http://www.cuj.com/documents/s=8042/cuj0002meyers/
Second, I don't think that there would be a big gain in productivity by
changing the polymorphic method syntax. As JG points out, it's not too much
work to ensure that the user of the code doesn't need to use that syntax, as
long as the library author is careful, so for instance
class virtual processor =
object
method virtual process : 'a . (#thing as 'a ) -> unit
end;;
class thing_processor =
object
inherit processor
method process obj =
begin
obj#quux;
print_string (string_of_int (obj#foo 1));
print_string obj#bar;
print_string (string_of_bool obj#baz);
print_endline ""
end
end ;;
and in any realistic program the virtuals will be in some separate module.
Having had a foot in the Ada world, I appreciate this little bit of verbosity
in which the typing is all laid out. My problem is not usually the issue of
changing text, but the issue of remembering what the types of things are.
-- Brian
-------------------
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:[~2003-08-21 0:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 15:42 Benjamin Geer
2003-08-20 16:05 ` Brian Hurt
2003-08-20 16:19 ` Richard Jones
2003-08-20 16:25 ` Benjamin Geer
2003-08-20 17:09 ` brogoff
2003-08-20 17:25 ` Jacques Carette
2003-08-20 23:34 ` Jacques Garrigue
2003-08-21 13:27 ` Jacques Carette
2003-08-20 18:19 ` Benjamin Geer
2003-08-20 20:39 ` brogoff
2003-08-20 21:04 ` Benjamin Geer
2003-08-21 0:28 ` Jacques Garrigue
2003-08-21 8:17 ` Benjamin Geer
2003-08-21 8:58 ` Jacques Garrigue
2003-08-21 9:38 ` Benjamin Geer
2003-08-21 11:44 ` Remi Vanicat
2003-08-21 13:11 ` Richard Jones
2003-08-21 16:41 ` Remi Vanicat
2003-08-21 18:04 ` brogoff
2003-08-21 20:20 ` Benjamin Geer
2003-08-21 23:35 ` Benjamin Geer
2003-08-22 3:59 ` Jacques Garrigue
2003-08-22 7:12 ` Benjamin Geer
2003-08-21 13:38 ` Benjamin Geer
2003-08-21 0:58 ` brogoff [this message]
2003-08-20 23:40 ` Benjamin Geer
2003-08-21 1:29 ` Jacques Garrigue
2003-08-21 9:19 ` Benjamin Geer
2003-08-21 18:44 ` Chris Clearwater
2003-08-20 20:43 ` Issac Trotts
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.44.0308201743530.20778-100000@grace.speakeasy.net \
--to=brogoff@speakeasy.net \
--cc=ben@socialtools.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