From: Diego Olivier Fernandez Pons <Diego.FERNANDEZ_PONS@etu.upmc.fr>
To: Brian Hurt <bhurt@spnz.org>
Cc: OCaml Mailing List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] algorithm question
Date: Sun, 26 Feb 2006 22:03:02 +0100 (NFT) [thread overview]
Message-ID: <Pine.A41.4.44.0602262159320.589968-100000@ibm1> (raw)
In-Reply-To: <Pine.LNX.4.63.0602261435090.9569@localhost.localdomain>
Bonjour,
> It's solving a problem that doesn't show up in functional programming.
It is orthogonal : FaCiLe is written in Caml and handles backtrack by
trailing (in other words it keeps only one copy of each object and
restores its state when needed).
On the other hand Gecode implements (partially) node sharing and is
written in C++
Diego Olivier
next prev parent reply other threads:[~2006-02-26 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 20:21 Michael Wohlwend
2006-02-26 20:48 ` [Caml-list] " Diego Olivier Fernandez Pons
2006-02-26 21:28 ` Michael Wohlwend
2006-02-26 20:51 ` Brian Hurt
2006-02-26 21:03 ` Diego Olivier Fernandez Pons [this message]
2006-02-27 10:30 ` Jean-Christophe Filliatre
2006-02-27 11:02 ` Diego Olivier Fernandez Pons
2006-02-27 14:48 ` Brian Hurt
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=Pine.A41.4.44.0602262159320.589968-100000@ibm1 \
--to=diego.fernandez_pons@etu.upmc.fr \
--cc=bhurt@spnz.org \
--cc=caml-list@yquem.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).