Any help you can offer for my aching cranium will be _much_
appreciated.
You might also be interested in the paper Edwin Brady and Kevin
Hammond just submitted to ICFP:
http://www.cs.st-andrews.ac.uk/~eb/drafts/icfp08.pdf
It describes how to manage resources, in particular locks, in a
On Thu, Apr 03, 2008 at 12:45:49AM +, Luke Palmer wrote:
2008/4/2 porrifolius [EMAIL PROTECTED]:
(7) ideally required permissions would appear (and accumulate) in
type signatures via inference so application code knows which are
required and type checker can reject static/dynamic
Hello.
I've been playing around trying to write a framework to support/enforce access
control to resources. So far my efforts have yielded little but bruised
forehead and compressed plaster-board.
What I'd like is a solution that:
(1) prevents access to resources except via a fine-grained
2008/4/2 porrifolius [EMAIL PROTECTED]:
(7) ideally required permissions would appear (and accumulate) in type
signatures via inference so application code knows which are required and
type checker can reject static/dynamic role constraint violations
If you mean what I think you mean by
