From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: caml-list@inria.fr
Subject: [Caml-list] classes, objects, and class variables
Date: Thu, 20 Nov 2003 22:07:14 +0900 [thread overview]
Message-ID: <20031120220714O.garrigue@kurims.kyoto-u.ac.jp> (raw)
To whom it may concern,
I'm in the process of improving the ocaml class system.
Principally the following two points:
1) making class creation cheaper.
If you believed you could create classes in a "let module", and
get away with it, you weere: it was prohibitively expensive in both
time and space. Now I'm seeing 10000% speeups.
2) using this to make objects (or final classes) first class.
Be able to write "let o = object (self) method m = ... end"
Side advantage, there are no restrictions on polymorphism.
But in this process, I came along with the rather strange behaviour of
class variables. Class variables are defined by a let before any
parameters, for instance
class c = let a = init () in fun ... -> object ... end
Their current semantics is to be evaluated repeatedly, once for c,
but again for all classes inheriting from c. The problem is that this
is costly for the implementation, doesn't fit well with the
possibility to create dynamically an arbitrary number of classes
inheriting from, and that I don't see what it's intended for.
So I'm planning to revert to the more intuitive semantics: evaluation
when creating c, but never again.
Does that bother anybody?
Jacques Garrigue
-------------------
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:[~2003-11-20 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 13:07 Jacques Garrigue [this message]
2003-11-20 15:53 ` Gerd Stolpmann
2003-12-23 7:37 ` 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=20031120220714O.garrigue@kurims.kyoto-u.ac.jp \
--to=garrigue@kurims.kyoto-u.ac.jp \
--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