From: John Prevost <prevost@maya.com>
To: Jerome Vouillon <Jerome.Vouillon@inria.fr>
Cc: Xavier Leroy <Xavier.Leroy@inria.fr>, caml-list@inria.fr
Subject: Re: Internals details for cmmgen.ml
Date: 23 Dec 1999 00:26:27 -0500 [thread overview]
Message-ID: <87so0uns70.fsf@isil.maya.com> (raw)
In-Reply-To: Jerome Vouillon's message of "Sat, 18 Dec 1999 19:56:35 +0100"
Jerome Vouillon <Jerome.Vouillon@inria.fr> writes:
> You could also probably make the permission check only once, when the
> region is created, and use the type system to enforce safety. For
> instance, the interface could look something like this:
>
> type 'a perms
> type 'a t
>
> val read_only : <read:unit> perms
> val write_only : <write:unit> perms
> val read_write : <read:unit;write:unit> perms
Oho! Nice trick. I'd thought of using the type system, but it hadn't
occurred to me that I could use object types in such a nefarious way!
Nice!
John.
prev parent reply other threads:[~1999-12-23 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-10 8:12 John Prevost
1999-12-11 18:09 ` Xavier Leroy
1999-12-18 0:51 ` John Prevost
1999-12-18 18:56 ` Jerome Vouillon
1999-12-23 5:26 ` John Prevost [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=87so0uns70.fsf@isil.maya.com \
--to=prevost@maya.com \
--cc=Jerome.Vouillon@inria.fr \
--cc=Xavier.Leroy@inria.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).