• Aucun résultat trouvé

XEROX SDD ARCHIVES

N/A
N/A
Protected

Academic year: 2022

Partager "XEROX SDD ARCHIVES "

Copied!
2
0
0

Texte intégral

(1)

To: Distribution

From: Dick Sweet

XEROX

BUSINESS SYSTEMS System Development Division

November 21, 1977

Subject: Mesa Language Working Group minutes

The Language Working Group met on 15 November, 1977. Monitors were discussed.

Recall the items

1. Independent FORK

2. Return type of a FORK

3. Questions of scope

4. Initialization of Monitors and condition variables

5. Monitor priority

XEROX SDD ARCHIVES

I have read and understood

Pages To

---

6. Condition timeout

7. Aborts Rev1ewer _________ Date

#

of Pages Ref., 7!&:J;~)

----

8. Interaction with SIGNALS

Item 1. Independent FORK.

Provide some system procedure to say "detatch" on the process. It could set the PSB so that joining would either fail or return immediately, or whatever is right.

Item 2. Return type of a FORK construct.

If pr: PROCEDURE [inrec] RETURNS [outrec] is forked, the value of the FORK construct is a

PROCEDURE RETURNS [outrec]; It could be internally be an indirect link into the PSB (with suitable alignment) so that aborting a process would be easier.

Items 5 and 6. Monitor Priority and Condition Timeout.

If simple (i.e. constant) default parameters are implemented for record declarations, then the priority or timeout can public fields and can be given in the declaration. This would require a change to the compiler to allow constructors for records with private fields.

Otherwise, all monitors are created with some default priority and a system procedure is provided to set it otherwise. The same is presumably true for condition timeouts

(2)

Item 7. Aborts.

Not part of the language.

Item 8. Interaction with SIGNALS.

After considerable discussion, it was decided that one would have to explicitly catch UNWIND in the monitor if it was thought possible that one could happen. The compiler would help by generating an "exit monitor" at the end of an UNWIND catchphrase within an entry procedure. On the subject of detecting the unwinding of a monitor without catching the signal, Butler suggested a sledge-hammer check of a bit in the code segment that says that there are some entry procedures in this segment.

2

Références

Documents relatifs

1 Published in Integrative Psychological and Behavioral Science 46, issue 3, 259-273, 2012 which should be used for any reference to this work. The original publication is available

Control subjects, for whom cervical afferent signals provide reliable information about head- trunk configuration, could transform the primary head- centered vestibular information

There are four basic message-handling operations provided by this scheme: Send Message, WaitForMessage, Send Reply, and AwaitReply. These queues are maintained in

Numbers fisted below are not true document numbers. See footnotes for

They are normal Mesa procedures (subroutines) that must have calling sequences as specified by CursorPnrType or PbkPnrType.. The routine CreateWindow makes one

The clearinghouses structure can fail in several ways. We take the approach that it is unnecessary to prevent failure, just so long as the structure puts itself

A project gets a unique project prefix which is identical to its ifs account. A project creates module libjects of the form <pilot>streams.mesa -- the

Domain knowledge. Three types of knowledge sources are often available in the problem domain: i) domain ontologies, which model the problem domain and offer rules and constraints