caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: bpr@best.com
Cc: caml-list@inria.fr
Subject: Re: OCaml's long range graphical direction?
Date: Fri, 09 Feb 2001 10:28:01 +0900	[thread overview]
Message-ID: <20010209102801K.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <Pine.BSF.4.21.0102081224310.18552-100000@shell5.ba.best.com>

From: Brian Rogoff <bpr@best.com>
> > This convoluted class and method system is intended to make using
> > lablgtk easier on the long term :-)
> > In fact, people seem to be coping with it OK. That is, I didn't get
> > that many questions on it. But certainly, there is a huge deficit in
> > documentation.
> 
> I just hack on the examples, but surely a bit more documentation would
> help. This might be good Consortium work, or even fixable with a volunteer 
> effort. 

Any volunteers ? Currently I have no time for documentation, sorry.
By the way, we can discuss that on the lablgtk list.

> After all of the admonitions against the use of Obj.magic it's a bit
> disconcerting to count 41 Obj.magic usages in lablgtk. I recall
> hearing that that will change. What's the plan?

Do not forget that any "external" declaration also amounts to an
Obj.magic, and there are 955 of them in lablgtk.
Seriously, most Obj.magic in lablgtk amount to a cast of an external
after checking its validity, and I see no way to avoid that.
What should disappear after ocaml 3.01 is release is the use of
     external coerce ... = "%identity"
which is an equivalent of Obj.magic used to go around some limitations
of the type system. There are 24 of them, but they will not be needed
anymore thanks to variance annotations in types.

Jacques
---------------------------------------------------------------------------
Jacques Garrigue      Kyoto University     garrigue at kurims.kyoto-u.ac.jp
		<A HREF=http://wwwfun.kurims.kyoto-u.ac.jp/~garrigue/>JG</A>



  reply	other threads:[~2001-02-09  9:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-05 17:48 Daniel Ortmann
2001-02-06  9:28 ` Xavier Leroy
2001-02-06 18:19   ` Sven LUTHER
2001-02-07 21:30     ` Pierre Weis
2001-02-08  7:32       ` Sven
2001-02-08  1:59     ` Jacques Garrigue
2001-02-08  7:55       ` Sven
2001-02-09  8:47         ` Claudio Sacerdoti Coen
2001-02-09 10:00           ` Sven LUTHER
2001-02-08 20:35       ` Brian Rogoff
2001-02-09  1:28         ` Jacques Garrigue [this message]
2001-02-09 18:11           ` Brian Rogoff
2001-02-10 13:01             ` Jacques Garrigue
2001-02-09 20:01           ` Marcin 'Qrczak' Kowalczyk
2001-02-12 14:52             ` Nicolas barnier
2001-02-12 23:47               ` Jacques Garrigue
2001-02-15 12:21                 ` [Caml-list] " Sven LUTHER
2001-02-08 10:28     ` Alan Schmitt
2001-02-09  1:24       ` bcpierce
2001-02-06 20:30   ` Dale Arntson
2001-02-07  0:39   ` John Max Skaller
2001-02-08 20:01   ` Francois Rouaix
2001-02-09  9:41     ` Sven LUTHER
2001-02-09  9:49     ` Jacques Garrigue
2001-02-09 19:58       ` Jerome Vouillon
2001-02-10 12:36         ` Jacques Garrigue
2001-02-10 21:25         ` Pierre Weis
2001-02-09 17:50     ` John Max Skaller
2001-02-06 19:33 Maxence
2001-02-09 23:31 Arturo Borquez

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=20010209102801K.garrigue@kurims.kyoto-u.ac.jp \
    --to=garrigue@kurims.kyoto-u.ac.jp \
    --cc=bpr@best.com \
    --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;
as well as URLs for NNTP newsgroup(s).