From: "Krishnaswami, Neel" <neelk@cswcasa.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Segfault in a native code multi-threaded program
Date: Mon, 20 Aug 2001 08:57:09 -0400 [thread overview]
Message-ID: <B1E4D3274D57D411BE8400D0B783FF322E86C5@exchange1.cswv.com> (raw)
David Mentre [mailto:David.Mentre@inria.fr] wrote:
> Brian Rogoff <bpr@best.com> writes:
> >
> > A more type safe marshaling framework is way up there on my list of
> > desired enhancements. I think this will be part of the extensional
> > polymorphism enhancements that you can see now in G'Caml.
>
> In my opinion, they are two different kinds of marshaling
> that one could expect: the safe one and the correct one. [...]
>
> I have probably missed something on the difficulty of marshaling. I
> tried to look at the mailing list archive, but did not find out the
> relevant messages. Any pointer?
Dumb observation. It seems to me that a lot of the simpler
marshalling problems -- tree-like structures with no closures -- can
be handled using a tool like the Zephyr project's ASDL (abstract
syntax description language).
http://www.cs.princeton.edu/zephyr/ASDL
I believe it has a mode to emit Caml, in addition to SML, Haskell
and Java. This ought to be able to handle a lot of cases with no
risk of core dumps. Code generation is a pain, of course, but it
seems to me to be preferable to core dumps.
--
Neel Krishnaswami
neelk@cswcasa.com
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2001-08-20 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 12:57 Krishnaswami, Neel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-16 8:08 David Mentre
2001-08-16 12:45 ` Vitaly Lugovsky
2001-08-17 8:09 ` David Mentre
2001-08-17 16:54 ` Brian Rogoff
2001-08-20 9:12 ` David Mentre
2001-08-20 16:54 ` Jun P. FURUSE
2001-08-18 23:15 ` John Max Skaller
2001-08-19 0:24 ` John Gerard Malecki
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=B1E4D3274D57D411BE8400D0B783FF322E86C5@exchange1.cswv.com \
--to=neelk@cswcasa.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