From: Patrick M Doane <patrick@watson.org>
To: caml-list@inria.fr
Subject: [Caml-list] New polymorphic variant syntax
Date: Wed, 21 Nov 2001 12:46:20 -0500 (EST) [thread overview]
Message-ID: <20011121122117.A10520-100000@fledge.watson.org> (raw)
Hello,
On the Bedouin project, we are currently exploring ways to verify that
construction of HTML data will respect constraints specified in a DTD. We
recently tried using the new polymorphic variant syntax in the 3.03 alpha
version to represent entity references. For example:
type fontstyle = [ `Tt | `I | `B | `U | `S | `Strike | `Big | `Small ]
type inline = [ `Pcdata | fontstyle | ... ]
type flow = [ block | inline ]
Then HTML generating functions use a phantom type to track the DTD
constraints:
val tt_ :
?id:string ->
?class_:string ->
(* ... more attributes follow ... *)
[< inline ] t list ->
[> `Tt] t
Having abbreviations like 'inline' works really well. I'm curious to know
if there is a good way to represent the following information:
<!ELEMENT FORM - - (%flow;)+ -(FORM)>
This states that a FORM element can have any flow object except for FORM
(i.e. nesting is not allowed).
How difficult would it be to extend the polymorphic variant syntax to list
tags that should not be included in the conjuction? Perhaps this already
possible? Of course we can always revert to simply listing the variants.
Thanks for the good work! This is much nicer to work with compared with
3.02.
Patrick
-------------------
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-11-21 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 17:46 Patrick M Doane [this message]
2001-11-21 19:06 ` Alain Frisch
2001-11-21 19:16 ` Patrick M Doane
2001-11-24 5:21 ` Mike Leary
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=20011121122117.A10520-100000@fledge.watson.org \
--to=patrick@watson.org \
--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