From: Don Syme <dsyme@microsoft.com>
To: "'David.Mentre@irisa.fr'" <David.Mentre@irisa.fr>, caml-list@inria.fr
Subject: RE: Use of BDDs in OCaml
Date: Wed, 19 Jan 2000 04:16:38 -0800 [thread overview]
Message-ID: <39ADCF833E74D111A2D700805F1951EF180143C9@RED-MSG-06> (raw)
I did one a while ago, but never polished it up. It was based on the CuDD
package. It may be useful as a starting point.
Perhaps BDDs should come as part of the standard distribution, as they do
with Mercury. OCaml could then easily become a standard platform for
implementing hardware verification tools. Does any one else have experience
as to which would be the best C package to lift to the OCaml level, or if
the performance gained by using C is worth it or not?
Cheers,
Don
> -----Original Message-----
> From: David.Mentre@irisa.fr [mailto:David.Mentre@irisa.fr]
> Sent: 17 January 2000 12:58
> To: caml-list@inria.fr
> Subject: Use of BDDs in OCaml
>
>
> Hi all dear Camlists,
>
> I would like to use BDD in a program of mine. So I'm looking for a BDD
> library that could be used in OCaml.
>
> Looking at mailing-list archive, I've found one implemented in 8,5 at
> LRI :
>
> ftp://ftp.lri.fr/LRI/soft/archi/Softwares/8,5/robdd.tar.gz
>
> I could also use a C BDD library (CMU's one for example) in access it
> from my OCaml program.
>
> Am I the first to do such a think? Is there another OCaml BDD library
> that I would have missed?
>
> Best regards,
> david
> --
> David.Mentre@irisa.fr -- PhD student -- PARIS research team
> Personal: http://www.irisa.fr/prive/dmentre/
> Professional:
> http://www.irisa.fr/paris/pages-perso/David-Mentre/anglais/
>
next reply other threads:[~2000-01-19 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-19 12:16 Don Syme [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-17 12:58 David Mentré
2000-01-24 21:20 ` Ken Friis Larsen
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=39ADCF833E74D111A2D700805F1951EF180143C9@RED-MSG-06 \
--to=dsyme@microsoft.com \
--cc=David.Mentre@irisa.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;
as well as URLs for NNTP newsgroup(s).