From: Jerome Vouillon <vouillon@clipper.ens.fr>
To: Francisco Valverde <fva@tsc.uc3m.es>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: Feature drawn back in new 1.06 version.
Date: Mon, 24 Nov 1997 17:27:56 +0100 (MET) [thread overview]
Message-ID: <Pine.SUN.3.95.971124172217.23729A-100000@vedette> (raw)
In-Reply-To: <34759E4C.1AE733A1@tsc.uc3m.es>
> I was using the possibity of defining recursive types for developing a
> rather convoluted search in two coupled domains, but now I find that I
> cannot anymore... Has anybody found a(n elegant, concise) way of
> circumventing it... Please note that the type recursion is ended by
> inserting appropriate non-recursive variants... Maybe I abused the type
> system! (Note also that a recursion at the level of structures would be
> heaven sent!)
> type p_state
[...]
> and p = (p_label, p_state, s) node
> and s = (s_label, s_state, p) node
You can change your type definitions as follow, and modify the
remaining of your program accordingly.
type p_state
[...]
and p = P of (p_label, p_state, s) node
and s = S of (s_label, s_state, p) node
-- Jerome
prev parent reply other threads:[~1997-11-24 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-21 14:44 Francisco Valverde
1997-11-24 16:27 ` Jerome Vouillon [this message]
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.SUN.3.95.971124172217.23729A-100000@vedette \
--to=vouillon@clipper.ens.fr \
--cc=caml-list@inria.fr \
--cc=fva@tsc.uc3m.es \
/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