Service Manuals, User Guides, Schematic Diagrams or docs for : xerox sdd memos_1977 19771202_Mesa_Language_Working_Group_Minutes
<< Back |
HomeMost service manuals and schematics are PDF files, so You will need Adobre Acrobat Reader to view : Acrobat Download
Some of the files are DjVu format. Readers and resources available here : DjVu Resources
For the compressed files, most common are zip and rar. Please, extract files with Your favorite compression software ( WinZip, WinRAR ... ) before viewing.
If a document has multiple parts, You should download all, before extracting.
Good luck. Repair on Your own risk. Make sure You know what You are doing.
Image preview - the first page of the document
>> Download 19771202_Mesa_Language_Working_Group_Minutes documenatation <<Text preview - extract from the document XEROX
BUSINESS SYSTEMS
System Development Division
December 2, 1977 XEROX SDD ARCHIVES
I have read and understood
To: Mesa Language Working Group Pages_________ To _________
Reviewer Date
From: Dick Sweet
{I of Pages
----
Ref .,t.1UJIf~; (;
Subject: Mesa Language Working Group minutes
The Language Working Group met on 23 November, 1977.
The discussion of object style monitors continued. A new type of procedure was proposed.
An INTERNAL PROCEDURE is a non-entry one that is called only when the monitor lock is,
held. For object style monitors, each INTERNAL procedure must begin with the same obi
parameter as must each ENTRY procedure.
WAIT, NOTIFY, and BROADCAST are allowed only from within an ENTRY or an INTERNAL
procedure. Is this also true for non object style?
A new type, LOCK, will exist with only one public field, priority. Thus we no longer need
MONITORED RECORDS, only ones with a LOCK in them. Likewise, CONDITION types have a
private field, timeout.
The discussion of long pointers began. One question was what sort of flavors of the
monitor stuff to do for various shaped pointers. There were 3 options.
1. Only LONG POINTER forms.
2. Short flavors for some or all.
3. Routines could take either. If they are done with a minimal stack, the interpreter
could use the stack size to determine whether the arguments are long or short.
◦ Jabse Service Manual Search 2024 ◦ Jabse Pravopis ◦ onTap.bg ◦ Other service manual resources online : Fixya ◦ eServiceinfo