From: Pixel <pixel@mandrakesoft.com>
To: John Max Skaller <skaller@ozemail.com.au>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Is a Cow an Animal?
Date: 18 Apr 2002 14:09:29 +0200 [thread overview]
Message-ID: <lyads1p5s6.fsf@leia.mandrakesoft.com> (raw)
In-Reply-To: <lyelhdpavj.fsf@leia.mandrakesoft.com>
Pixel <pixel@mandrakesoft.com> writes:
[...]
> http://merd.net/pixel/language-study/various/is-a-cow-an-animal/ocaml.listing
> uses a variant for the kind (I just changed it, it was a string)
>
> I've still kept the class to allow sharing of fields.
>
> BUT this solution doesn't allow a stricter checking alike ocaml2.listing or
> c++2.listing. The reason is that you can't parameter the class with values
> (like (Vegetable Carrot)) only types.
>
> Maybe this is possible with polymorphic variants (?), I'll try...
done: http://merd.net/pixel/language-study/various/is-a-cow-an-animal/ocaml3.listing
it's quite nice. The advantage over the all-in-class solution is that it's
easier to check the types:
* one pb was:
let is_meat_ = function
| `Beef | `Dead_rabbit | `Dead_human -> true
| _ -> false
which type "[> `Beef | `Dead_rabbit | `Dead_human] -> bool" doesn't allow
is_meat_ (food : [`Grass])
whereas
let is_meat e = is_meat_ (e :> food_kind)
is_meat (food : [`Grass])
is allowed (since is_meat : [< food_kind] -> bool)
* I still can't manage to have:
new_human : int -> ([ `Dead_human], [< food_kind]) animal
all i got is
new_human : int -> ([ `Dead_human], _[< food_kind]) animal
Please help!
-------------------
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:[~2002-04-18 12:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 23:40 Pixel
2002-04-18 2:17 ` John Max Skaller
2002-04-18 10:19 ` Pixel
2002-04-18 12:09 ` Pixel [this message]
2002-04-18 12:52 ` Jacques Garrigue
2002-04-18 13:03 ` Pixel
2002-04-18 18:58 ` james woodyatt
2002-04-18 22:44 ` Pixel
2002-04-18 22:57 ` james woodyatt
2002-04-18 23:31 ` Pixel
2002-04-19 0:21 ` Remi VANICAT
2002-04-19 0:51 ` james woodyatt
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=lyads1p5s6.fsf@leia.mandrakesoft.com \
--to=pixel@mandrakesoft.com \
--cc=caml-list@inria.fr \
--cc=skaller@ozemail.com.au \
/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;
as well as URLs for NNTP newsgroup(s).