From: fva@die.upm.es (Francisco Valverde Albacete)
To: caml-list@margaux.inria.fr
Subject: Some questions and proposals...
Date: Wed, 16 Feb 94 10:54:22 +0100 [thread overview]
Message-ID: <9402160954.AA18004@lorien.die.upm.es> (raw)
Hello mailing list,
I hope you don't get discouraged when you see the number of question I
address you...
1) Has anybody developed a module for trees with a variable number of
branches? If so, can I borrow it?
My own solution comes from Reade's:
(* Variable trees *)
type 'a vtree = Vtree of 'a * 'a vtree list;;
type 'a forest = 'a vtree list;;
though, for the sake of efficient updating I have used mutables in the
design (yes, the nasty "can't generalize type.." etc.
I would also thank any ideas for the functionals around the
base type. I have already done some: it_vtree, exists_vtree,
for_all_vtree, do_vtree in the spirit of their list counterparts...
OOPS, I must say I'm coding it in CAML (Heavy)!
2) This is a question mainly to CAML and Camllight implementors: has
anybody thought of a way to migrate in an automatic, or at least semi-
automatic way, modules from one of the systems to the other? I have this
huge quantity of modules in CAML wanting to be compiled in Camllight...!
3) Finally (or so I think), I guess many of us have types and functions
that could be of use for the rest ("reuse" they call it, I think).Is
there anythihg like a freeware repository for CAML and Camllight
modules?
If so, where? If not, could we discuss such a thing? At least a list
or sort of FAQ for people whom to ask for them? I volunteer to receive
and compile a list of people and things (cut and paste, you know) and
send the list back to caml-mailing-list. That'd be something to start
with!
Hope the mail comes in handy for someone else! Au revoir mailing-list!
Francisco Valverde
fva@die.upm.es
next reply other threads:[~1994-02-16 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-02-16 9:54 Francisco Valverde Albacete [this message]
1994-03-01 17:55 ` Vale'rie Me'nissier-Morain
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=9402160954.AA18004@lorien.die.upm.es \
--to=fva@die.upm.es \
--cc=caml-list@margaux.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