From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Alternate constructors for a class
Date: 02 Sep 2003 18:07:39 +0200 [thread overview]
Message-ID: <1062518859.1092.17.camel@ares> (raw)
In-Reply-To: <20030902134537.GA7309@redhat.com>
Am Die, 2003-09-02 um 15.45 schrieb Richard Jones:
> I have a class defined currently like this:
>
> class view ?width ?height ?packing ?show ?(title = "untitled") () =
> (* ... *)
>
> I want to provide an alternate way of constructing this class, in this
> case by unmarshalling it from a channel (using the Marshall module).
> Callers should be able to construct a view either using the explicit
> parameters, or by doing:
>
> let chan = open_in_bin "serialized_class" in
> let view = new view ~chan in
> (* ... *)
>
> Now in the case above I guess I could add an extra optional ?chan
> argument, but that seems a bit ugly because it doesn't prevent users
> from supplying incorrectly both ~chan and ~title, for example.
>
> Is there an easy way to provide two different constructors for a
> class?
>
> Other languages do allow different sets of arguments to different
> constructors for the same class quite naturally.
You may consider a union type, e.g.
type view_intf = View_explicitly of (int * int * ...)
| View_from_channel of in_channel
class view (intf : view_intf) =
let (width, height, ...) =
match intf with
View_explicitly(w,h,...) -> (w,h,...)
| View_from_channel ch -> ...
in
object ... end
class view_explicitly ?width ?height ... =
view (View_explicitly(width,height,...))
class view_from_channel ch =
view (View_from_channel ch)
Ok, this is not very natural, but at the end the way of implementation
is hidden from the users.
Other options would be independent implementations of view_explicitly
and view_from_channel, which is possible if both classes have the same
type (which is very natural in O'Caml but not in other languages), or
you can also try to map view_from_channel directly to view, e.g.
class view_from_channel ch =
let (width, height, ...) = ... unmarshal ch ... in
view ~width ~height ...
You could also inherit from virtual classes only providing components of
view, and by different ways of inheriting you get different interfaces.
Just be creative.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de
------------------------------------------------------------
-------------------
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
prev parent reply other threads:[~2003-09-02 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 13:45 Richard Jones
2003-09-02 15:11 ` Michal Moskal
2003-09-02 16:07 ` Gerd Stolpmann [this message]
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=1062518859.1092.17.camel@ares \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/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