From: katre <katre@henchmonkey.org>
To: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Subclasses and pattern matching
Date: Fri, 19 Sep 2003 11:22:52 -0400 [thread overview]
Message-ID: <20030919152252.GA30989@henchmonkey.org> (raw)
In-Reply-To: <20030919145220.GD4205@redhat.com>
Richard Jones wrote:
>
> Possibly I'm being dumb here, but wouldn't it be better to use
> a union type, eg:
>
> type num = Int of int | Float of float
>
Yes, except for two facts:
a) Each different type has different data available (some are ints, some
strings, some more complex)
b) Each different type has a lot of data. I don't really want to
specify a 10-member tuple for each constructor :)
c) Where the data is used, I want to match two or three different types,
and then call a default method with anything left over. With a union, I
have to deal with every possible type, or do nothing with the data.
To clarify, using your type above, I can't do
match n with
Int(i) -> print_int i
| _ -> print_int some_data_from_n
Remember, all of my structures have many more than 1 piece of data. A
class inheritance really is the best way to model the data structure, I
just want to be able to pattern match on it.
katre
-------------------
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-09-19 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 14:21 katre
2003-09-19 14:52 ` Richard Jones
2003-09-19 15:22 ` katre [this message]
2003-09-19 15:58 ` art yerkes
[not found] ` <20030919155431.GA31387@henchmonkey.org>
2003-09-19 16:32 ` art yerkes
2003-09-19 16:40 ` Claude Marche
2003-09-20 15:00 ` Michal Moskal
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=20030919152252.GA30989@henchmonkey.org \
--to=katre@henchmonkey.org \
--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