File information: | |
File name: | 19771202_Mesa_Language_Working_Group_Minutes.pdf [preview 19771202 Mesa Language Working Group Minutes] |
Size: | 59 kB |
Extension: | |
Mfg: | xerox |
Model: | 19771202 Mesa Language Working Group Minutes 🔎 |
Original: | 19771202 Mesa Language Working Group Minutes 🔎 |
Descr: | xerox sdd memos_1977 19771202_Mesa_Language_Working_Group_Minutes.pdf |
Group: | Electronics > Other |
Uploaded: | 17-10-2019 |
User: | Anonymous |
Multipart: | No multipart |
Information about the files in archive: | ||
Decompress result: | OK | |
Extracted files: | 1 | |
File name 19771202_Mesa_Language_Working_Group_Minutes.pdf 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. |
Date | User | Rating | Comment |