From: Vincent BARAT <vincent.barat@alcatel.fr>
To: caml-list@inria.fr
Subject: alloc_final() and alloc()
Date: Tue, 22 Dec 1998 12:03:35 +0100 [thread overview]
Message-ID: <367F7C87.3E08B590@alcatel.fr> (raw)
Hi !
I'm new to the list and I am working on a project whose aim is
to permit to write CORBA client and servers in Objective ML
on top of a generated stub (ML and C++) that works under VisiBroker
for the moment but should work with any ORB with very few modifications
(because the generated stub is on top of the C++ mapping of CORBA).
This project is very near to its end (3 or 4 days now !). What I could
say for the moment is that it is far more easy to write clients and
servers
in ML than with C++ !!!
So, I've discovered a problem with alloc(): it seems to return
always the same address if it is used several times in the same function
that contains also calls to alloc_final().
Is it a known bug ? If not, am I missing something ?
Thanks for your answer.
P.S. : for the moment, instead of calling alloc(), I call alloc_shr()
which work well concurrently with alloc_final().
next reply other threads:[~1998-12-22 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-22 11:03 Vincent BARAT [this message]
1998-12-22 18:33 ` doligez
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=367F7C87.3E08B590@alcatel.fr \
--to=vincent.barat@alcatel.fr \
--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