From: james woodyatt <jhw@wetware.com>
To: The Trade <caml-list@inria.fr>
Subject: [Caml-list] functional objects
Date: Fri, 18 Oct 2002 17:54:45 -0700 [thread overview]
Message-ID: <5BF65502-E2FD-11D6-B29D-000393BA7EBA@wetware.com> (raw)
everyone--
Before I file a wish request for this, I'd like to spark a discussion
about it.
I really like the functional object semantics in Ocaml. I think
they're way cool. I'm having a great time exploring what I can do with
them. Nothing really mindblowing to show for it yet, but give me time.
Anyway, one of the things I find lacking is a way to call a subclass
constructor in the copy constructor. In other words, I'd like to have
some way to do the following:
(* class type with only public methods exposed *)
class type foo = object method f: unit end
(* class with private members *)
class foo x : foo = object
val x: int = x
method f = ()
end
(* derived functional subclass (notice method g) *)
class bar y = object
inherit foo 0
val y: int = y
method g a b = {< foo a; y = b >}
end
What I want is for a superclass class to be able to expose an interface
to subclasses for constructing copies with arguments. Is this a bad
idea? Has it already been considered and rejected? Just curious.
--
j h woodyatt <jhw@wetware.com>
markets are only free to the people who own them.
-------------------
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 reply other threads:[~2002-10-19 0:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 0:54 james woodyatt [this message]
2002-10-19 20:48 ` Didier Remy
2002-10-21 4:10 ` james woodyatt
2002-10-21 6:55 ` Didier Remy
2002-10-21 18:40 ` james woodyatt
2002-10-22 8:42 ` Didier Remy
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=5BF65502-E2FD-11D6-B29D-000393BA7EBA@wetware.com \
--to=jhw@wetware.com \
--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