Subject:
|
Re: Clarification of access control
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Fri, 17 Nov 2000 03:40:37 GMT
|
Viewed:
|
1757 times
|
| |
|
|
In article <G44yFL.1LG@lugnet.com>, "Dave Baum" <dbaum@enteract.com>
wrote:
> One way to think of this is that losing resources is a C++/Java style
> exception, and an acquire statement implicitly has a catch with no
> action...
>
> acquire(X)
> {
> ...body...
> }
>
> is sort of like
>
> try
> {
> grabResource(X);
> ...body...
> }
> catch (ResourceLostExcetion e)
> {
> }
I forgot to show that resources get released, the functionality is more
like this:
try
{
grabResource(X);
...body...
releaseResource(X);
}
catch (ResourceLostException e)
{
}
Dave
--
reply to: dbaum at enteract dot com
|
|
Message is in Reply To:
 | | Re: Clarification of access control
|
| If a task loses its resources (due to an equal or higher priority task acquiring them), then control leaves the body of the acquire statement. If there is a "catch" block following the acquire, then the catch block is executed, otherwise control (...) (26 years ago, 16-Nov-00, to lugnet.robotics)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
