From: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] troubles with polymorphic variant in class
Date: Mon, 14 Jun 2004 10:37:54 +0100 [thread overview]
Message-ID: <20040614093754.GA7925@redhat.com> (raw)
In-Reply-To: <1087142756.10383.50.camel@Bess>
On Sun, Jun 13, 2004 at 06:05:57PM +0200, François-Xavier HOUARD wrote:
> So, as every composant can have different type of father, every object
> is parametrized by the type of his father, for example, a button in a
> panel in a window is, for the moment, typed as
> window panel button
> as the button class looks like that:
> class ['a] button (father:'a)
> ....
> and the panel too,etc
>
> I find it nice, cause every widget has got his "genealogic tree" in his
> type.
I'm probably missing something here, but what's wrong with having
every widget just contain an ordinary data item / method pointing to
the parent? eg. button#parent == panel ?
Rich.
--
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
C2LIB is a library of basic Perl/STL-like types for C. Vectors, hashes,
trees, string funcs, pool allocator: http://www.annexia.org/freeware/c2lib/
-------------------
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:[~2004-06-14 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 16:05 François-Xavier HOUARD
2004-06-13 17:59 ` skaller
2004-06-14 9:29 ` François-Xavier HOUARD
2004-06-14 9:48 ` Damien Doligez
2004-06-14 15:49 ` skaller
2004-06-14 9:37 ` Richard Jones [this message]
2004-06-14 14:48 ` nakata keiko
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=20040614093754.GA7925@redhat.com \
--to=rich@annexia.org \
--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