caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "kyra" <kyrab@mail.ru>
To: "Nicolas Cannasse" <warplayer@free.fr>, "OCaml" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCam'OLE pre-release
Date: Sat, 3 Aug 2002 14:47:56 +0300	[thread overview]
Message-ID: <000d01c23ae3$9dd62700$551aa8c0@kyra> (raw)
In-Reply-To: <001101c23a0d$2f184220$0700a8c0@warp>

Again. Ocaml can GC any variable thas is no longer used 'as an ocaml
variable'. But it turns out the underlying object is still used 'as COM
object'. In the case of olegen may this be a bad design of oleaut32 server?
Anyway, 'automatic' solution does not exist, so if we map ocaml 'finalize'
to COM 'Release', we must maintain some 'discipline' trying to reference
ocaml variable somewhere if we know it is still used as COM object. Hmm. If
so, where in olegen.ml is this problem buried?

-------------------
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


  parent reply	other threads:[~2002-08-03 10:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 19:19 Nicolas Cannasse
2002-07-31 12:06 ` [Caml-list] OCam'OLE pre-release (mirror) Nicolas Cannasse
2002-07-31 12:48   ` Samuel Lacas
2002-07-31 13:13     ` Nicolas Cannasse
2002-07-31 13:30       ` Samuel Lacas
2002-08-01 23:39 ` [Caml-list] OCam'OLE pre-release kyra
2002-08-02 10:13   ` Nicolas Cannasse
2002-08-02 23:26     ` kyra
2002-08-02 23:23       ` Quetzalcoatl Bradley
2002-08-04 12:00         ` kyra
2002-08-03 11:47     ` kyra [this message]
2002-08-05  7:46       ` Nicolas Cannasse
2002-08-05  9:32         ` Xavier Leroy
2002-08-05  9:51           ` Nicolas Cannasse
2002-08-06 12:15             ` kyra
2002-08-07  8:55               ` Nicolas Cannasse

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='000d01c23ae3$9dd62700$551aa8c0@kyra' \
    --to=kyrab@mail.ru \
    --cc=caml-list@inria.fr \
    --cc=warplayer@free.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).