Copyright c Xerox Corporation 1980Inter-Office MemorandumToMesa UsersDateOctober 27, 1980FromJohn WickLocationPalo AltoSubjectMesa 6.0 Change SummaryOrganizationSDD/SS/MesaXEROX Filed on: [Iris]Doc>Summary60.bravo (and .press)This memo outlines changes made in Mesa since the last release (Mesa 5.0, April 9, 1979). The firstsection lists references which should be consulted for more detailed information. The secondsection contains an overview of the changes. The final section describes operational differenceswhich you must know in order to use Mesa 6.0.For most programs, you should be able to begin converting to Mesa 6.0 after reading only thismemo; then consult the various updates when details of new features are required. If yourapplication relies on the extended memory support previously provided by XMesa, you willprobably need to read the System and XMesa updates before converting.ReferencesThe following documents can be found on Doc>. (In Palo Alto, the official Mesa release directoryis maintained on Iris (there is also a copy on Ivy); in El Segundo, it is on Isis. For other locations, consult your supportgroup.) In addition, the file Mesa60.press is a compilation of this and other material (about 75pages); hardcopy is available through your support group.Mesa 6.0 Change Summary. Summary60.pressMesa 6.0 Compiler Update. Compiler60.pressMesa 6.0 Binder Update. Binder60.pressMesa 6.0 System Update. System60.pressMesa 6.0 XMesa Update. XMesa60.pressMesa 6.0 Debugger Update. Debugger60.pressMesa 6.0 Utilities Update. Utilities60.pressMesa 6.0 Pup and Ftp Update. PupFtp60.pressThe above memos describe changes since the last release. The Doc> directory also includesnew versions of the following documents:Mesa System Documentation. System.pressMesa Debugger Documentation. Debugger.pressMesa User's Handbook. Muhb.pressMesa Pup Package Functional Specification. Pup.pressН!вОpТX qpН]Оg~rТiНІОcsН]pТX Н-єsН7BpНІО]ШsН]pН-єsН7BpНІОYsН]tН-єsН7Bp НЭОSЛupНЇОMЪsТFП6НЇОGлpТ│ПIТ┌НЇОF$ТвП;ТьП"НЇОD}ТЎТ©ПNНЇОBжТП-НЇО?┤Т╦П%Т╧П8НЇО=ЮТЮТАПDНЇО<8ТТПHТУНЇО:▒ТПEНЇО6Kr НЇО2ЩpТ▐П'Т░v pwП2НЇО1yТ│ПFТ┌П7НЇО/УpТ÷vpТ═П1НЇО.MТП9НґО*ЪxТXpvНґО)xpvНґО'#xpv НґО%5xpv НґО#GxpvНґО!YxpvНґОkxpvНґО}xpv НЇО/pТ┐П=Т└v pНЇО┤ТП(НґО9xТXpvНґОKxpv НґО]xpv НґОoxП)pv√Эр=Гd Mesa 6.0 Change Summary2Mesa Ftp Functional Specification. Ftp.pressIntegrated Mesa Environment. CommandCentral.press (in Utilities60.press)Performance Mesaurement Tool. PerformanceTool.pressControl Transfer Counting Tool. XferCounter.pressDebugger: Extended Features. XDF.press (in Debugger60.press)Because the language changes are upward compatible with Mesa 5.0, a new version of the MesaLanguage Manual will not be issued with this release; consult the Compiler Update and the BinderUpdate for information on additions to Mesa and C/Mesa.HighlightsThe primary emphasis in this release has been on the following areas:A number of significant new language features are included: extended defaults, floating pointsupport, machine dependent records and enumerated types, dynamic storage allocation, sequences,and exported types. Less major revisions and extensions have been made in the following areas:syntactic and semantic glitches, keyword array constructors, packed array representation, successorand predecessor operations, the DIRECTORY statement, implicitly imported interfaces, type TEXT, loopcontrol variables, extended NIL, the REJECT statement, and the ABORTED signal. The languagechanges are compatible with Mesa 5.0, and will not affect existing source code (there are some minorexceptions; see below). In addition, the Compiler's user interface and command line syntax havechanged substantially. See the Compiler Update and Appendix A of the Mesa User's Handbook fordetails.A Mesa source formatter is available with this release. It establishes a standard representation forsource text, and will produce both plain and formatted .bravo and .press files. Completedocumentation can be found in Appendix B of the Mesa User's Handbook.The Binder has been updated to agree with the Compiler's treatment of the DIRECTORY statementand its user interface and command line syntax. In addition, it now supports multiple controlmodules in a single configuration. See the Binder Update and Appendix C of the Mesa User'sHandbook for details.Support for extended memory beyond 64K, formerly provided by XMesa, is now part of thestandard system. The BasicMesa configuration has been abandoned in favor of facilities whichdynamically delete non-essential components of the system. Support for subdirectories, fastdirectory scanning, floating point, Pup checksums, and 3K RAMs have been added. (Appendix G ofthe Mesa User's Handbook details extensions made to RunMesa.) Other than memory allocationfacilities, changes to the System and Pup and Ftp interfaces are minor; see the updates for details.The Debugger has a new user interface, a new interpreter, and a simple cut and paste editor. TheDebugger's command language is essentially unchanged, but several extensions in windowoperations and source window facilities have been added. A description of the new FileTool isattached to the Debugger Update.Several new commands have been added to the Lister, and the IncludeChecker has been extensivelymodified to support large configurations more efficiently. A new package, CommandCentral, isavailable for use with the Debugger; it serves as a small executive for controlling the editing,compilation, binding, and debugging of applications software. This package greatly speeds up theeditcompilebinddebug cycle when small changes are involved. Documentation is attached tothe Utilities Update.НЇОfЯtТНGОНґОbxТXП!pvНґО`0xpvpvpНґО^BxpvНґО\TxpvНґОZfxpvpvpНЇОWТ╠ПOТ╡xНЇОUpТ√pП2Т≈xpxНЇОSиpТП1НЇОO┐r НЇОL5pПEНЇОHФТэП1ТщП,НЇОG?Т╔П1ТіП.НЇОE≈Т╗ПBТ╘НЇОCПТўПCТ╞НЇОBIТ└Т┘spП1spНЇО@║ТжspspspТвНЇО>ЗТ║ПOwНЇО=SТрpП-ТсНЇО;╚Т▄Т█xpxpНЇО:НЇО6╣Т·ПaТ÷НЇО5ТиП7vpvpТй НЇО3gТП0xpНЇО0ТёТєП/sp НЇО.qТдТеПWНЇО,иТ╩П"Т╪ xpx НЇО+"pТНЇО'сТжП"ТвП4НЇО&,ТеП-ТфП0НЇО$┘ТЪП2ТП*НЇО"щТ┐П:wpТ└НЇО!6Т╛xТґpПCНЇО▐Т≈П)Т≤П;НЇО@Т▓Т⌠ПUНЇО≥Т&ПOТ'НЇОЯТґП9ТўypНЇОJТxpНЇОШТ└П7Т┘П(НЇОTТ√Т≈П8y pНЇОґТоТпПJНЇОТ║ПSТ╒ НЇО ^Т▒П>Т▓НЇОЇТxp XЇp=Г\⌡oMesa 6.0 Change Summary3A new mode has been added to the Control Transfer Counting Tool which allows modules to beassigned to groups and information to be collected on cross group as well as cross module transfers.The performance measurement tools are documented separately as described in the first section ofthis memo.Operational ChangesThis section summarizes important operational differences which you must know in order to useMesa 6.0; do not begin to convert to Mesa 6.0 until you have read it. More complete information iscontained in the update memos listed in the first section of this document.GeneralOn large programs, performance of the Mesa 6.0 Compiler and Debugger on 64K Altos isconsiderably worse than in Mesa 5.0; an extended memory machine with a minimum of 128K isrecommended.Alto Operating System version 18 and Executive version 11 or later are required to run Mesa 6.0.The new file creation date standard is now supported. The compiler inserts the creation date of thesource file into the .bcd (as does the Binder), and the Debugger checks that the source and objectfile versions match. The IncludeChecker also makes use of these dates. Therefore, you must use aneditor and a file server that support the file date standard. If you use dump files, be sure you havethe latest version of Ftp.LanguageWith two exceptions, Mesa 5.0 source files are compatible with Mesa 6.0. In file names in theDIRECTORY statement, names inside angle brackets are no longer ignored; they are treated assubdirectories of the Alto file system (use of this feature is not recommended). The following newreserved words have been added: FREE, PRED, PROC, REJECT, SEQUENCE, SUCC, UNCOUNTED, andZONE.CompilerThe order of evaluating the items in constructors (including argument lists) and the operands ofinfix operators (except AND and OR) has been changed, particularly in cases involving embeddedprocedure calls; it is no longer always left to right. In particular, expressions of the form word _get[s]*256+get[s] are suspect, and probably incorrect.Except during initialization, constructors for records containing MONITORLOCKs, CONDITIONs, andPORTs are not allowed (to prevent unintentionally overwriting these fields with their default values).Such records must be assigned to fieldbyfield.For element sizes of four bits or less, the internal representation of packed arrays has changed.This is a potential problem in reading files containing packed arrays created by earlier versions ofMesa.The Compiler no longer supports interactive command input; it reads commands only from thecommand line, and does not use the keyboard or display (limited feedback is via the cursor). Thecommand language has been extended and switch processing has changed. The /c switch has beendeleted; global switches must now be specified with a null file name, e.g. Compile /p Defs Impl.НЇОfЯtТНGОНЇОbpТёПEТєНЇО`vТ┬П5Т┴П/НЇО^оТ²П!Т·П?НЇО](Т НЇОXБrНЇОU■pТЁП!ТЄП<НЇОSЛТ▄xПГ]▓:Mesa 6.0 Change Summary4Switches are restricted to a single letter. Do not use complete switch names such as /pause (eachletter will be interpreted as a separate switch). Until you understand the full syntax of thecommand language, it is best to group all global switches at the beginning of the command linefollowing a single slash.The log is now written on Compiler.log, not Mesa.typescript; separate .errlog files arestill produced. The error log (if any) is deleted if the compilation is successful; conversely, if thecompilation fails, the .bcd (if any) is deleted.The implementation of floating point has changed considerably; the IEEE standard format is nowused, and the compiler generates calls directly to user-supplied microcode (this will produceundefined results if the proper microcode is not loaded). Calls to software floating point as in Mesa5.0 can be generated with the /-f switch. Do not use type REAL without first consulting with thesupplier of your floating point package.Because of bug fixes, previously acceptable programs may no longer compile.BinderThe Binder is now available only as a .bcd file; you must have Mesa.image to run it. Like theCompiler, the Binder takes commands only from the command line and does not use the keyboardor display; it writes its log file on Binder.log.The meaning of switches used to copy code and symbols has changed substantially; read the BinderUpdate if you use these options. Compressed symbols have been compressed still further to includeonly procedure and signal names (without parameters or results); this substantially reduces the sizeof these .symbol files.Because of bug fixes, previously acceptable configurations may no longer bind.SystemMesa 6.0 is compatible with XMesa 5.0 microcode version 39 (but some new features are notavailable with the old microcode; e.g., extended memory BITBLT).Features previously implemented by BasicMesa and XMesa are now a standard part ofMesa.image. MakeImage is no longer a part of the standard system; ImageMaker must beloaded or bound with the client configuration if it is needed.The standard system now supports only command line input; the MesaExec can be loaded toprovide interactive input. The command line switch /b can be used to convert the standard systemto a basic one. The /k switch will disable the allocation of space for the Debugger's bitmap onextended memory machines (see below).The default maximum numbers of processes (75) and modules (384) have been increased. Aversion of the System called SmallMesa allows 33 processes and 256 modules.Interface changes are described in the System Update.ЪНЇОfЯtТНGОНЇОbpТ≥П+Т xП)vpНЇО`vТАПPТБ НЇО^оТ╞П%Т╟П9НЇО](ТНЇОYыТ²Т·vpvp vp НЇОX2Т÷П*Т═П=НЇОV┼ТvpНЇОS<Т╒П^НЇОQ■ТРП2ТСП+НЇОOМТ│Т┌ПGНЇОNFТёvp xsxТєП"НЇОL·ТП(НЇОIPpПKНЇОEQtНЇОBpТ▒П&vpv pТ▓НЇО@[Т▐ПBТ░НЇО>ЁТП&v pНЇО;eТ┼Т▀П;xНЇО9ҐpТ┘Т├ПKНЇО8Т≈ПdНЇО6oТvpНЇО3 ПNНЇО/!tНЇО+рpТнП/ТоП*НЇО*+ТП8spНЇО&эТ2П0Т3П!НЇО%5v pТ╗ypП,Т╘y pНЇО#▌ТП>НЇО ?Т╩П-Т╪ypНЇО≤Т┤Т┬vpП+НЇОПТ╗vpП,Т╘НЇОIТП%НЇОЗТжПTТвНЇОSТypП%НЇОП'xpЪ FЇҐ=ГUN!Mesa 6.0 Change Summary5DebuggerThe Debugger has also been enhanced to take advantage of extended memory. If you have morethan two banks (128K) of memory, see the installation section of the Debugger Update for anexplanation of the options available; otherwise, the standard defaults will "do the right thing".The Debugger now requires a strike font named SysFont.strike or MesaFont.strike; aversion of Gacha10 is available on MesaFont.strike. Additional fonts are available on[Maxc]. (Strike fonts that include kerning are not supported.)The selection scheme and the assignment of function keys and mouse buttons has changed.Clicking RED once selects a character, clicking twice selects a word, three times a line, etc.; theselection can be extended to the left or right with BLUE. The menu button is now YELLOW(formerly BLUE). FL4 is no longer the stuff key; use FR4 (Spare2) or Keyset2.Scrollbars no longer occupy a dedicated part of the window, but instead come up on top of the leftedge. To obtain a scroll bar, move left just past the edge of the window, then move right slightly,back into the window.New source window menu commands have been added, and they have been factored into severalmenus. The Debugger's wisk window has been replaced by a more general Split menucommand. There are now also Normalize Insertion and Normalize Selection commands.The interpreter can now be used when in Display Stack and Display Process subcommandmode. Several commands now invoke the interpreter automatically (e.g., Octal Read: @p, n:SIZE[R]). The interpreter does procedure calls (the Interpret Call command has beendeleted).The constructs ABS, ERROR, LONG, LOOPHOLE, MAX, MIN, NIL, POINTER TO, PROC, PROCEDURE, SIGNAL,WORD, and open and half open intervals have been added to the interpreter's grammar. Typeexpressions following % must be enclosed in parentheses. The interpreter syntax Expression?replaces the Interpret Expression command.Each breakpoint is now assigned a unique number used for displaying and clearing it. There arenew commands for attaching conditions to break and tracepoints. Break/Tracepoints can no longerbe set by typing a source line, and the Break Module and Break Procedure commands andcorresponding Trace and Clear commands have been deleted; the menu commands must beused. Clear All Entries/Xits clears both break and tracepoints.Tracepoints now automatically invoke the normal Display Stack command processor (withsubcommand p(arameters), v(ariables), or r(esults) as appropriate). The q(uit)subcommand (not b(reak)) exits to the Debugger's command level; it no longer continuesexecution of the client.If the source window is loaded with the s(ource) subcommand of Display Stack, the windowwill remember the appropriate context for setting breakpoints. For an exit break, the s(ource)subcommand now displays the declaration line of the procedure.The Debugger no longer ignores case, and the case commands have been deleted; identifiers must betyped with their correct capitalization.НЇОfЯtТНGОНЇОbНЇО^оpТ⌡П#Т°П8НЇО](Тк ТлП7xpНЇО[─ТмПaНЇОX2ТеП"Тфv pvpНЇОV┼Т⌠Т■vpП$НЇОTЦvpТП9НЇОQ■ТПТЯП?НЇОOМТҐspПSТЎНЇОNFТзП.ТшspsНЇОL·pТ spspП!spspspНЇОIPТ┴Т┼ПEНЇОG╗Т▓Т⌠ПRНЇОFТНЇОB╡ТєП>Т╔НЇОAТЫП"ТЗП%vpНЇО?dТ│vpvp НЇО<Т▒Т▓vpvp НЇО:nТ╚П@Т╛vНЇО8фpТБП.v pТЦНЇО7НЇО3пТ┌spspspspspspspsТ┐pspspspНЇО2)spТе ТфПLНЇО0┌ТІypП&ТЇy НЇО.зpТvpНЇО+▄Т║Т╒ПPНЇО)ДТ█Т▌ПFНЇО(=Т╙П(vpvpНЇО&√Тф vpТгvpП6НЇО$НТvpП#НЇО!═ТХП0vpНЇОЬТН vpv pТОvpvНЇОQpТМvpП?НЇО╙ТНЇО[Т▀П'Т▄vpvpНЇОЄТёП1ТєП&vНЇОpТП>НЇОЎТ│П:Т┌xНЇОТП(ФЇ │>ГZ┼tMesa 6.0 Change Summary6Distribution:Mesa UsersMesa GroupSDSupportНЇОfЯtТНGОНІОbpН хО`vТX Н хО^о Н хО](ЪBІ\АЧ*$Copyright c Xerox Corporation 1980Inter-Office MemorandumToMesa UsersDateOctober 27, 1980FromEd SatterthwaiteLocationPalo AltoSubjectMesa 6.0 Compiler UpdateOrganizationPARC/CSLXEROX Filed on: [Iris]Doc>Compiler60c.bravo, Compiler60d.bravo, and Compiler60.pressThis memo describes changes to the Mesa language and compiler that have been made since therelease of Mesa 5.0 (April 9, 1979).Definitions of syntactic phrase classes used but not defined in this document come from the MesaLanguage Manual, Version 5.0, Appendix F.CompatibilityBecause of changes in symbol table and BCD formats, you must recompile all existing Mesaprograms after obtaining recompiled versions of the interfaces and packages that they depend upon.Language ChangesOur goal for language compatibility has been to accept any valid Mesa 5 source program as a validMesa 6 source program. We are aware of the following incompatibilities:There are some new reserved words, as follows:FREE PRED PROC REJECT SEQUENCE SUCC UNCOUNTED ZONESome of the quoted file names that appear in DIRECTORY clauses have differentinterpretations. Text inside angle brackets is no longer ignored; it is treated as the name of alocal subdirectory (but we do not recommend using local subdirectories for Mesa programs atthe present time).The orders of evaluating the items in constructors (including argument lists) and the operandsof infix operators (except AND and OR) have changed somewhat. In particular, programs thatassumed a left-to-right order of procedure calls in these contexts (e.g., Divide[Pop[], Pop[]]) areunlikely to work correctly.The assignment operation is no longer available for updating objects containing MONITORLOCKor CONDITION values; updating of such objects must be done component-by-component.The granularity of packed arrays has changed. If the components of a packed array can bestored in four or less bits, the storage structures defined by the declaration of that array willdiffer between Mesa 5 and Mesa 6. This is a potential problem in reading files created byearlier versions of Mesa. Also, the DESCRIPTOR operator cannot be applied to packed arraysoccupying less than a word.ЪН!вОpТX qpН]Оg~rТiНІОcsН]pТX Н-єsН7BpНІО]ШsН]pН-єsН7BpНІОYsН]tН-єsН7BpНЭОSЛupНЇОN#sТFПTНЇОG╗pТ╙П4Т╚П'НЇОFТП$НЇОB╡Т⌡П[Т°wНЇОAТpНЇО;оrНЇО8─pТХП"ТИspП.НЇО6ыТ┴П3Т┼П/НЇО2ІtТXНЇО/hpТ▌ПaНЇО-юТПHНLО+EТXП.НBО(йsТFПGНLО&OpТGП-spТHНLО$╗Т▀ПSТ▄ НLО#Т█П[НLО!YТНLОчТ┼П^НLО7Т▓spspТ⌠П0НLО░Т┤П*Т┬wpwpwpНLОХТНLОmТ▀П3Т▄s НLОфpТПspП)ТЯНLОKТ║ПYНLОєТ П\Т⌡НLОЭТ╔ПOТі НLОUТ⌡Т°s pП,НLОўТ≤Эр=Гd Mesa 6.0 Compiler Update2If you have been using type REAL, check with the supplier of your floating point package todetermine the effect of Mesa 6 changes in that area.Bug FixesA large number of Mesa 5 bugs have been fixed. The most notable of these involveexpansion of inline procedures that are defined in DEFINITIONS modules,expansion of inline procedures when an argument is itself an expanded inline,proper retention of the tag of a variant record within an arm of a discriminating selection,proper identification of object files that have been renamed.Because of certain bug fixes, the compiler may reject previously acceptable programs or may issuenew warning messages.As usual, the list of compiler-related change requests closed by Mesa 6.0 will appear separately aspart of the Software Release Description.Language RationalizationMesa 6 attempts to remove certain minor anomalies and to add some obvious generalizations to theexisting language.Syntactic Glitches RemovedList Punctuation: For most lists that are explicitly bracketed by symbols other than [ and ], theallowable forms are described by the following meta-BNF:list ::= empty | item | item separator listIn other words, the list may be empty or may be a sequence of items separated by, and optionallyterminated by, a separator. This rule now applies to the following constructs: form separator notesVariantList,CatchSeries;ANY must come lastChoiceSeries;ExitSeries;StatementSeries;StmtChoiceSeries;ChoiceList,ExprChoiceList,When the bracketing symbols are [ and ] or when the length of a list is significant, a trailingseparator is not allowed unless it is semantically meaningful (as in constructors and extractors), butempty lists are allowed. This change affects the following syntactic entities:UsingClause: The form USING [ ] is now permitted (e.g., to emphasize that an interface isonly being exported).VariantFieldList: In the declaration of a variant record, the form [ ] (empty brackets) maybe used instead of NULL (and is recommended).ЪНЇОfЯtТНGОНLОbpТ Т⌡spП;НLО`vТП4НЇО\TtТXНЇОYpПQНLОV┼П3s pНLОTПMНLОQ■П\НLОOП=НЇОKкТ°Т²ПDНЇОJ#ТНЇОFуТ÷П6Т═П-НЇОE-ТП)НЇО?ЯrТiНЇО<╒pТ┼ПIТ▀НЇО:ШТНЇО6ыtТXНЇО3┼wТґpП.ТўП#НЇО1ЦТП8НLО/hxpТXНеxpxpxНЇО,МpТ■Т∙ПHНЇО+EТПOНґО(йwТXНеp wН'сwНґО&Ox Н лpНґО$╗x Н лpН'сspНґО#xН лpНґО!Yx Н лpНґО╡xН лpНґОxН лpНґОcx Н лpНґО╪x Н лpНЇОmТхПTТи НЇОфТ∙П"Т√ПDНЇОТПOНLОєx pТ⌠spТ■П;НLОЭТНLО │xpТ▓П6Т⌠НLОзТspЪЭЇ⌠=Г\xMesa 6.0 Compiler Update3FieldList: The form [ ] is permitted in the declaration of a ParameterList orReturnsClause (it is equivalent to omitting the list or clause).Directory: The form DIRECTORY ; may be used in place of an empty directory.ImportsList (ExportsList): The form IMPORTS (EXPORTS) may be used when thecorresponding list is empty.The last two items reflect the view that DIRECTORY, IMPORTS and EXPORTS introduce formal parameter lists,even though their punctuation omits [ and ].Declarations in Loop Bodies: A declaration series can now appear between DO and ENDLOOP (afterthe OPEN and ENABLE clauses, if any); no additional bracketing is required. Its scope is limited tothe DeclarationSeries and StatementSeries in the loop body.A Bit Less VerbiagePROC: PROC is accepted as a short form of PROCEDURE.Statement Brackets: The bracket pair { } can be used any place the bracket pair BEGIN END canbe used (but not conversely).Semantic Glitches RemovedLONG Arithmetic: Compile-time evaluation of expressions with constant operands now works for 32-bit quantities just as it does for 16-bit quantities.Dereferencing with OPEN: A pointer expression following OPEN or WITH will be dereferenced anarbitrary number of times (not just once) to obtain an expression designating a record.Renaming with OPEN: An OPEN clause may give an alternative local name to an interface that itopens (formerly, only to a record).Nested Extractors: An ExtractItem may itself be an Extractor. This allows extraction from recordsembedded within records. In particular, this form is useful in situations where a single-component record is notautomatically converted to its single component, e.g., extraction from a record that is the only component of a returnrecord.Extractor Expressions: An assignment with an Extractor as its left side may be used as anexpression. This allows, among other things, multiple extraction. The value of such an assignmentis the value of its right side.Interface Aliases: An interface module may have multiple identifiers (preceding ": DEFINITIONS").In the DIRECTORY clause of another module, you can reference that interface using any one of theidentifiers. A type obtained from such an interface is equivalent to the same type obtained througha naming path that uses any other identifier of the interface.НЇОfЯtТНGОНLОbxpТ'Т(П&xpНLО`vxpТП3НLО]ШxpspП/НLО[─x pТ\x pspspТ]НLОYыТНLОW│vТ┬Т┴svsvsvП"НLОV!ТП,НЇОRУwТ▒pТ▓П+spspНЇОQNТ≥spspП.Т П#НЇОOїТxpxpНЇОK└tТXНЇОH6spspspНЇОDГwТ├pП3Т┤spspНЇОC@ТНЇО?tТXНЇО;оswТ─ pТ│ПPНЇО:'ТП5НЇО6ыwТІspП"spТЇspНЇО51ТПWНЇО1ЦwТ╘ spspП0Т╙НЇО0;ТП#НЇО,МwТ┌px p Т┐xpП&НЇО+EТ·vТ÷ПDНЇО)аТєПoТ╔НЇО(`НЇО%5wТэpxpТщНЇО#▌Т▐ПBТ░П!НЇО!ФТНЇО≤wТ╔pТіП-s pНЇОПТ Т⌡spПPНЇОIТ┤ПSТ┬НЇО╒ТП> *Ї[>ГN╟*Mesa 6.0 Compiler Update4New Language FeaturesExtended DefaultsYou can associate a default initial value with a type (not just with a field of a record). If a type isconstructed from other types using one of Mesa's type operators (e.g., RECORD), the default valuefor that type is determined by the default values of the component types and by rules associatedwith each operator. When you declare a named type, you have the option of explicitly specifying adefault for that type.With this extension, you will find that uses of defaults in Mesa generally fall into two classes.Default values for fields of records make the corresponding constructors more concise and moreconvenient to use. On the other hand, the usual reason for associating a default initial value with atype is to ensure that storage allocated for that type is well-formed, i.e., that any variable of such atype always has a meaningful value. There is some interaction between these uses; the default valueof a record type is partly determined by any default values specified for its fields, and a record fieldmay inherit its default value from the type of that field. The details appear below.The rules for inheritance of defaults are designed to provide the following property (currently notquite preserved by sequence or variant record types): if a type T has been given a non-NULL defaultvalue, any type derived from T will have a defined and non-NULL default value for any embeddedcomponent of type T. Because of the potential cascading effect implied by this, you shouldcarefully consider the relative costs and benefits of specifying a default, especially one that does notinclude NULL as an alternative.Defaults are ignored in determining equivalence and conformance of types. Thus it is possible tohave two compatible types with different default initializations.Specification of Default InitializationNone of the built-in types (INTEGER, CARDINAL, BOOLEAN, CHARACTER, STRING and REAL) has adefault initial value.The following rules determine the default initial value of a type designated by an expressioninvolving a type operator:The default initial value for a type constructed using RECORD (or ARRAY) is defined field-by-field (or element-by-element). For each field (element), it is the default value for that field ifthere is one; otherwise, it is the default initial value for the type of that field (element) or isundefined if there is no such default.The default initial value for any port type, constructed using PORT, is NIL (see below).Types constructed using other operators have no implied default initialization.The default initial value of a type designated by a declared type identifier T depends upon the formof the declaration of T, as follows:T: TYPE = TypeExpr; T receives all the attributes of TypeExpr including any default.T: TYPE = TypeExpr _ e; T receives all the attributes of TypeExpr except that its default initial value is e.НЇОfЯtТНGОНЇОaвrТiНЇО]╣tТXНЇОZfpТ▌П#Т▐ПEНЇОX©ТіПGsp ТїНЇОWТ╗Т╘ПEНЇОUpТ┬Т┴ПOНЇОSиТНЇОPzТфП;ТгП&НЇОNсТІПMТЇНЇОM,Т┬П&Т┴П@НЇОK└Т░П,Т▒П<НЇОIщТ─ Т│ПYНЇОH6Т┐П%Т└ПCНЇОF▌ТПUНЇОC@Т÷Т═ПVНЇОA≤Т├Т┤П%wpspНЇО?ЯТ≈wpТ≤spНЇО>JТшwp ТэП>НЇО<╒Т┼ПZТ▀ НЇО:ШТspНЇО7╛Т·П#Т÷П>НЇО6ТПAНЇО2ІwТXП'НЇО/hpТхТиspspspspspspНЇО-юТНЇО*rТшП1ТэП,НЇО(йТНLО&OТ≈Т≤spspНLО$╗Т┬Т┴ПZНLО#Т√П@Т≈П#НLО!YТП&НLОчТXП?spspНLОcПOНЇОТ┌ПAТ┐wpНЇОmТwpН@ОРwpТXspwpН@ОwwpwpН@ОЭwpspwpwpН@О │wpwpП*wp┌Ї :>ГZяLMesa 6.0 Compiler Update5ExamplesFlag: TYPE = BOOLEAN _ FALSE;Rec1: TYPE = RECORD [f: Flag];-- default value is [f: FALSE]Rec2: TYPE = RECORD [f: Flag] _ [ ];-- ditto (the field defaults)Rec3: TYPE = RECORD [f: Flag] _ [TRUE];-- explicit defaultRec4: TYPE = Rec3;-- default value is [f: TRUE]Rec5: TYPE = Rec3 _ [f: FALSE];-- default value is [f: FALSE]Any DefaultSpecification is acceptable in a type declaration (see Mesa Language Manual, Version5.0, page 37). A declaration giving a type T a NULL default cannot, however, equate T to a typewith a default that does not include NULL. A default appearing in a type definition within aDEFINITIONS module must be either NULL or an expression with a compile-time constant value.Default values associated with types are usedto initialize local variables of procedures and programs, in the absence of explicit initialization,to initialize variables that are dynamically allocated using NEW, in the absence of explicitinitialization (see below),to construct records (except argument and result records), in the absence of an explicit valuefor a field in the constructor and of a default value for that field in the record declaration,to construct arrays, in the absence of an explicit value for an element (see below).Defaults in Argument and Result RecordsYou may specify default values for the fields of argument and result records. Such default valuesmust be constructed from constants or variables that are declared outside of the procedure typedefinition. In particular, you cannot use a value of another field of the same record or, in the caseof a result record, a value from the associated argument record to define such a default. You may omit a field in the constructor of an argument or result record only if the definition ofthat record specifies an explicit default value for the field; default initial values associated with thetypes of such fields are not inherited (for example, this protects you from assigning a value to areturn variable and then forgetting to mention it in a RETURN statement, causing the default for itstype to be returned). On the other hand, protection against ill-formed storage is inherited; you maynot void or elide a field unless the type of that field allows a NULL initialization. Any defaults that you specify in the declaration of a result record serve two purposes. Since thefields of such a record can be used as local variables within the procedure body, a defaultspecification affects the initialization of those variables; in addition, it allows abbreviation in theconstructors of the corresponding return records. The precise rules are the following:Upon entry to a procedure, each field of the result record is initialized with the default valuespecified for that field, if any; otherwise, with the default initial value for the type of thatfield, if there is one; otherwise, its initial value is undefined.If a RETURN is followed by an explicit constructor, the default specifications appearing in thedeclaration of the result record control the values of any omitted or elided fields, even if otherassignments have been made to the result variables within the procedure body. If the RETURNstands by itself, without such a constructor, or if the RETURN is implicit, the return record isconstructed using the current values of the result variables. НЇОfЯtТНGОНюОbwН@О_ёpТXspspspН@О]ШwpspspwpН.зwspН@О\TwpspspwpН.зН@ОZґwpspspwpspН.зН@ОYwpspwpН.зwpspН@ОW^wpspwpwspН.зwpspНЇОTТ√xpТ≈П'wНЇОRhpТєП!Т╔wpspП!wp НЇОPаТмП%spТнП(НЇОOs pТрТсspП5НЇОKкТXП-НLОIPТ┌П<Т┐П(НLОFуТкТлП&spНLОE-ТНLОB╡Т≥ПIТ НLОAТіП9ТїП&НLО>░ТПTНЇО;AwТXП'НЇО7СpТ П=Т⌡П%НЇО6KТ╨П/Т╩П0НЇО4єТ█ПfНЇО2ЩТПZНЇО/ўТ╒ ТёПSНЇО.Т∙ПUТ√НЇО,_wpТ╟wpТ╠П.НЇО*╦Т∙П7sp Т√НЇО)Т┐Т└П7wpНЇО'iТПAspНЇО$ТіПbНЇО"sТХТИП@НЇО лТ╦ПgНЇО%ТПWНLО╙Т▐ПZТ░НLОТ╟Т╠ПDНLО[ТПBНLОЮТ≈spТ≤П9НLО9Т┤ПLwpwТ┬НLО▒Т║Т╒П8psНLОЙpТ°П-Т² spП"НLОCТП> ЇЭ=ГX─Mesa 6.0 Compiler Update6ExamplesT: TYPE = INTEGER _ 1;Proc1: PROC [i: INTEGER _ 0, j: T];Proc2: PROC RETURNS [m: T, n: INTEGER _ 2] = { -- m initialized to 1 (from T), n to 2 Proc1[j: 3];-- Proc1[i:0, j:3]; Proc1[i: 3];-- illegal (j does not default to 1) ... m _ 4; n _ 5; ... RETURN;-- returns [4, 5] ... RETURN [m, n];-- also returns [4, 5] ... RETURN [m];-- returns [4, 2] ... RETURN [NULL, n];-- illegal (declaration of T disallows voiding of m) ... RETURN [, n];-- ditto (m does not default to 1 or 4) ... RETURN [6, 7];-- returns [6, 7] ... };-- implicitly returns [4, 5]Defaults and Variant RecordsYou may specify a default for the entire variant part in the declaration of a variant record type. Inthe absence of such a specification, the default value of that part, including the tag, is undefinedwith respect to the undiscriminated record type.The default initial value of a discriminated variant record type has a tag value corresponding to thediscriminating adjective, and defaults for the other fields of the variant part are those implied by thefields selected by that tag. In particular, the declaration or allocation of a variable with discriminated record typesets the tag correctly.ExampleVRec: TYPE = RECORD [ common: INTEGER _ 0, variant: SELECT tag: * FROM red => [r1: BOOLEAN _ FALSE], green => [g1: INTEGER _ 0] ENDCASE _ red[TRUE] | NULL];v: VRec;-- initial value is [common: 0, variant: red[r1: TRUE]]v1: VRec _ [common: 10];-- initial value is [common: 10, variant: red[r1: TRUE]]v2: VRec _ [variant: NULL];-- tag and variant part are undefined, v2.common = 0v3: VRec _ NULL;-- illegal (declaration of common does not allow NULL)rv: red VRec;-- initial value is [common: 0, variant: red[r1: FALSE]]gv: green VRec;-- initial value is [common: 0, variant: green[g1: 0]]Defaulted Array ElementsElements in an array constructor may be voided or elided. Omission of elements is permitted in akeyword constructor (see below) but not in a positional constructor. The empty constructor ([ ]) is akeyword constructor with all items omitted. An elided or omitted element receives the default valuefor the type of the components of the array (if any); the value of a voided element is undefined.ALL abbreviates a positional constructor of the appropriate length; thus ALL[ ] elides all elements(defaulting if possible) and ALL[NULL] voids all positions.ЪНЇОfЯtТНGОНЇОbwНLО_ёpТXspspНLО](wpspwpspwpwpНLОZґwpspspwpwpwpspНLОYwpwpwpwpНLОW^wpwpН лwpwpwpНLОUЇwpwpН лwpНLОTНLОRhwpwpНLОPаsТFpН лТXНLОOsТFpТXwpwpН лНLОMrsТFpТXwpН лНLОKкsТFpТXspwpН лwpwpНLОJ#sТFpТXwpН'с wpwpНLОH|sТFpТXН лНLОFуН лНЇОC├wНЇО@7pТ┴П5Т┼П1НЇО>░Т╗Т╘ПOНЇО<ИТП0НЇО9 Т▄П4Т█П1НЇО7СТ─Т│ПKНЇО6KТ■vП1Т∙П*НЇО4гТНЇО1°wНLО/!pТXspspНLО-zwpspНLО+рwpspwpsНLО*+pwpwpspspНLО(└wpwpspНLО&эspwpspspНLО$awpwpН лwpwpwpwpspНLО"╨wpwpwpН лwpwpwpwpspНLО!wpwpwpspН лП'wpwpНLОkwpwpspН лwpspНLОдwpwpН лwpwpwpwpspНLОwpw pН лwpwpwpwpНЇОнwНЇОpТ▓П.Т⌠П3НЇОьТ│П#Т┌ПCНЇО1Т─П"Т│ПBНЇО┴Т╒ПBТёНЇО ;spТЁП8ТЄ spНЇО⌠ТspspЪ ─ЇL=Г\©ИMesa 6.0 Compiler Update7Keyword Array ConstructorsYou can use keyword array constructors when the index type of the array is an enumeration orsubrange thereof. The acceptable keywords are the constants appearing in the enumeration. In thecase of a subrange, the endpoints must be defined by expressions involving only those constants, theoperators FIRST, LAST, SUCC and PRED, and identifiers equated by declaration to such expressions.If the component type of the array has a defined default value (including NULL), keyword items canbe omitted; the corresponding elements receive the default value.Packed ArraysIf you specify the PACKED attribute for an array type, the granularity of packing is 1, 2, 4, 8 or 16nbits and is determined by the component type of the array (formerly just 8 or 16n bits).The value of the construct SIZE[T, n] is the size, in words, of the storage required by a packed arrayof n items of type T. (SIZE[T] continues to yield the number of words occupied by a single item oftype T.)ExampleBit: TYPE = BOOLEAN _ FALSE;BitSet: TYPE = PACKED ARRAY Color OF Bit;AllBits: BitSet = ALL[TRUE];threeBits: BitSet _ [yellow: TRUE, red: TRUE, blue: TRUE]; Successor and Predecessor OperationsThe operators SUCC and PRED operate upon values of any ordered type except REAL. For numericand character types, SUCC[x] and PRED[x] are equivalent to x+1 and x1 respectively. Forenumerated types, the values are the successor and predecessor of x in the enumeration; a boundsfault occurs if there is no such element and you requested bounds checking.DirectoriesYou can now override the association established by the DIRECTORY clause between the names ofincluded modules and the names of the files containing those modules. Any file names implied byconvention can be omitted entirely; they will be computed from the interface identifiers.SyntaxIncludeList::=IncludeItem|IncludeList , IncludeItemIncludeItem::=identifier UsingClause|identifier : FROM FileName UsingClause|identifier : TYPE UsingClause|identifier : TYPE identifier UsingClauseUsingClause::=empty | USING [ IdList ] | USING [ ]The (initial) identifier in an IncludeItem names a module. If you specify the name of the filecontaining that module when you invoke the compiler (as a keyword parameter with keywordidentifier, see below), that name is used, even if a FileName appears in the IncludeItem.Otherwise, if such a FileName appears, it is used. If you supply neither a compile-time argumentnor a FileName, the name identifier.bcd is used.НЇОfЯtТНGОНЇОbТXНЇО^оpТЄП:Т╣П"НЇО](Т┼ПIТ▀НЇО[─Т┌ПUТ┐НЇОYыТ╔ spТіspspspП=НЇОX2Т┴Т┼П2spНЇОV┼ТПAНЇОRhtТXНЇОOpТ█spТ▌П;wНЇОMrpТЭП/ТЩП!wpНЇОJ#Т├spwpwpТ┤П>НЇОH|Т┴wpwpspwpП(Т┼НЇОFуТwpНЇОC├wНLОApТXspspspНLО?dwpspsТFpТXwpspwpНLО=╪wpwpspspНLО<w pwpwspwpspwpspНЇО7СtП$НЇО4єpТ⌠ spspП(Т■sp НЇО2ЩТчspwpspwpТъwpwpНЇО1UТ≤Т≥П-wpНЇО/ўТП)wpНЇО+▄t НЇО(=pТ╗П7Т╘spНЇО&√Т▌П`НЇО$НТПYНЇО"swНLОЬx Н лpН'сx Н лОQН'сТXНLОж Н лpН'сxН лО/Н'сsxН лО┤Н'сsxН лОЮН'сsxНLОe Н лpН'сxsx sxНЇОpТІ x pТЇx pП5НЇОoТяП7ТрП!НЇО хx pТЭТЩxpx pНЇО Т≤xpТ≥П'НЇО yТxp y pЪ эЇ 2>Г]ы▐Mesa 6.0 Compiler Update8One approach to describing systems built from collections of Mesa modules views the DIRECTORYclause as the declaration of (compile-time) formal parameters of type TYPE. Mesa 6 provides thefinal two forms of IncludeItem primarily for compatibility with this view. The identifier precedingthe colon names the formal parameter; it is also used to derive a file name as described above. Theidentifier following TYPE constrains the set of acceptable actual parameters; it must match theModuleName used in the definition of the module that you intend to include (see the MesaLanguage Manual, Version 5.0, Section 7.2).You can use the final form to change the name by which one module is known within another,notably to avoid duplicate names in a DIRECTORY clause. For example, you might need to referencetwo different versions or parameterizations of an interface Defs within a single program. TheIncludeItemsLongDefs: TYPE Defs,ShortDefs: TYPE Defsdeclare LongDefs and ShortDefs as identifiers within that program of possibly different modules,each with the ModuleId Defs. As IncludeItems, the formsidentifieridentifier: TYPEeach abbreviateidentifer: TYPE identifierand the name in the DIRECTORY must be identical to the ModuleId if you use one of these forms.Implicitly Imported InterfacesAn implicitly imported interface is one from which imported values are required for binding thefree variables of another, explicitly imported interface. For example, interface D1 might importinterface D2 to gain access to a procedure or exported variable supplied by the latter. D2 is thenimplicitly imported by any program module M that imports D1 (see the Mesa Language Manual,Version 5.0, Section 7.4.4).In Mesa 6, the free variables of D2 that are used by D1 are bound to the principal instance of D2 inM. An import is a principal instance if it is the only instance of that interface imported by amodule or if it is unnamed. Furthermore, if M imports no instances of D2, a principal instance willbe created automatically. If module M has no other reason to mention D2, D2 then need notappear in either the DIRECTORY or the IMPORTS list of M. Explicitly importing a principal instanceof D2 in such a situation is not an error, and you must do so ifyou plan to use positional notation to specify the imports of M in a C/Mesa configurationdescription, since the positions of automatically created interface instances are not defined, oryou already import more than one instance of D2, each of which is named.In a C/Mesa configuration, principal instances of interfaces are not supplied automatically; you must import themexplicitly if they cross (sub)configuration boundaries. ЪНЇОfЯtТНGОНЇОbpТ╗П"Т╘П2sНЇО`vpТїПEТ╗spНЇО^оТ▀x pТ▄x p НЇО](Т┌П0Т┐П4НЇО[─x pТя spП<Тр НЇОYыx pТуПIТжwНЇОX2ТpНЇОTЦТўП6Т╞П$НЇОS<Т┐П%Т└spП2НЇОQ■ТъТЮП&wpНЇОOМx pНLОMrwpТXspwНLОKк pspwНЇОIPpТЁwpwpТЄП,НЇОG╗Т xpwpx pНLОE-w НLОC├ pТXsНЇОApНLО>░w pspw НЇО<pspxpНЇО7СtНЇО4єpТўП_НЇО2ЩТ╦ Т╧ПDwpНЇО1UТ⌡ wpП!Т°П,wpНЇО/ўТєТ╔wp wp wНЇО.Т pНЇО*╦Т│П!wpwpwpТ┌wpНЇО)wpТ╪П*ТҐП5НЇО'iТ┐wpП$wpwpТ└НЇО%бТ╪П$ТҐwpwpwp НЇО$Т▓Т⌠spspwpП,НЇО"sТwpП;НLОЬТґП>wpТўНLОQТ▓Т⌠ПAНLОжТП-wpНЇО╚vТхПAzvТиНЇО'ТП8p ▌ЇЮ=ГQ+`Mesa 6.0 Compiler Update9Real NumbersMesa 6 has adopted the proposed IEEE standard for floating-point arithmetic (see, e.g., Coonen, Animplementation guide to a proposed standard for floating-point arithmetic, Computer, January 1980,pp. 68-79). In support of this, the language provides floating-point literals and the compilerperforms a limited number of operations upon floating-point constants.Syntaxprimary::=... | realLiteralrealLiteral::=unscaledReal|unscaledReal scaleFactor|wholeNumber scaleFactorunscaledReal::=wholeNumber fraction| fractionfraction::=. wholeNumberscaleFactor::=E optSign wholeNumber | e optSign wholeNumberoptSign::=empty | + | wholeNumber::=digit | wholeNumber digitAn unscaledReal has its usual interpretation as a decimal number. The scaleFactor, if present,indicates the power of 10 by which the unscaledReal or wholeNumber is to be multiplied toobtain the value of the literal.Mesa 6 represents REAL numbers by 32 bit approximations as defined in the IEEE standard. Therounding mode used to convert literals is "round-to-nearest." A literal that overflows the internalrepresentation is an error; one that underflows is replaced by its so-called "denormalized"approximation. In Mesa 6, the value of the unscaledReal in a literal must be a valid LONGINTEGER when the decimal point is deleted.No spaces are allowed within a realLiteral. Note that such a literal can begin, but not end, with adecimal point. Thus the interpretation of [0...1) is unambiguous (but perhaps surprising; use [0 .. .1)or [0.0..0.1) instead).OperationsThe compiler performs the following operations involving floating-point constants:Unary negation (with 0 = 0)ABSFixed-to-Float (in "round-to-nearest" mode).Other operations are deferred until runtime, even if all their operands are constant, so that theprogrammer can control the treatment of rounding and exceptions (see the proposed standard).Unless you specify the compilation option -f (see below), the compiler generates instructions for floating-pointoperations that require hardware or microcode support. If you are in doubt about the state of your machine orits microcode, see a local floating-point expert.ЪНЇОfЯtТНGОНЇОbТXНЇО^оpТ└П-Т┘П5НЇО](Т█ПKwpНЇО[─ТчТъПSНЇОYыТПFНЇОW^wНLОTЦxН лpН'сxТXНLОRh Н лpН'сxН лОPаН'сН лОOН'сНLОL·Н лpН'сxН лОJВpН'сxНLОH|Н лpН'сxНLОF Н лН'сП-НLОC├Н лН'сНLОA Н лН'сНЇО=╪pТёxpТєП4x pНЇО<ТаП'xpx pТбНЇО:nТНЇО7Т²spТ·ПGНЇО5xТ═Т║ПGНЇО3пТПBТНЇО2)ТлП,xpТмsНЇО0┌pТП#НЇО-3Т▐x pТ░П)НЇО+▄Т─П*Т│П>НЇО)ДТНЇО&√w НЇО#GpПRНLО лТXxpНLО%sНLО}pП,НЇОТ©ПaНЇО[ТхП?ТиНLОvТ╟П,Т╠ПDНLОёТ⌠ПkТ■НLОBТП1┬Ї=ГSЛMesa 6.0 Compiler Update10Machine Dependent EnumerationsSometimes a programmer can enumerate the values of some type but requires control of theencoding of each value or of the number of bits used to represent the type (usually for futureexpansion). Mesa 6 provides machine-dependent enumerations for such applications.SyntaxEnumerationTC::=MachineDependent { ElementList }MachineDependent::=empty | MACHINE DEPENDENTElementList::=Element | ElementList , ElementElement::=identifier|identifier ( Expression )|( Expression )ExamplesStatus: TYPE = MACHINE DEPENDENT {off(0), ready(1), busy(2), finished(4), broken(7)}Color: TYPE = MACHINE DEPENDENT {red, blue, green, (255)}-- reserve 8 bitsEach Expression in an EnumerationTC must denote a compile-time constant, the value of which isan unsigned integer.In an enumerated type with the MACHINE DEPENDENT attribute, the values used to represent theenumeration constants are assigned according to the following rules. If a parenthesized expressionfollows the element identifier, the value of that expression is used; otherwise, the representation ofan element is one greater than the representation of the preceding element. If you specify only arepresentation, the corresponding element (normally a place holder) is anonymous. If therepresentation of the initial element is not given, the value zero is used.You cannot explicitly specify the representation of any element unless the attribute MACHINEDEPENDENT appears in the type constructor. Two element identifiers cannot be represented by thesame value (either given explicitly or determined implicitly as described above). The ordering ofelements determined by position in the ElementList must agree with the ordering determined bythe (unsigned) arithmetic ordering of the representations.Sparse EnumerationsA machine-dependent enumerated type is sparse if there are gaps within the set of values used torepresent the constants of that type or if the smallest such value is not zero. Mesa 6 takes thefollowing position on gaps: they are filled by valid but anonymous elements of the enumeratedtype. These elements can be generated only by the operators FIRST, SUCC and PRED (or by theiteration forms that implicitly use these operators).If you use a sparse enumerated type as the index type of an array, the array itself will havecomponents for all elements of the enumeration, including the anonymous ones. The latterare awkward to access (except through ALL) and may cause problems in constructors,comparison operations, etc., as well as wasted space. (For example, ARRAY Color OF INTEGERwould occupy 256 words.)ЪНЇОfЯtТНG?НЇОbТXНЇО^оpТзТшП>НЇО](ТҐТЎПNНЇО[─ТПRНЇОYwНLОV┼xН лpН'сxpТXx pНLОTxН лpН'сxsТFНLОQ■x Н лpН'сxpТXx pxНLОOН лpН'сx Н лОMrpН'сx px pН лОKкН'сx pНЇОIPwНLОFуpspsТFpТXwpwpwpwpwpНLОDZwpspsТFpТXwpwpwpН5АНЇОAТ┌x pТ┐xpП;НЇО?dТНЇО<ТҐТЎspП,НЇО:nТ⌡ПEТ°НЇО8фТ√П<Т≈П*НЇО7Т° Т²ПXНЇО5xТПRТ НЇО3пТПKНЇО0┌ТМП3ТНП"sНЇО.зpТ≥ПSТ НЇО-3ТїТ╗ПJНЇО+▄Т╘П&Т╙x pП+НЇО)ДТП:НЇО&√wТXНЇО#GpТ═П'wpТ║П&НЇО!═ТЄТ╣ПTНЇОЬТ╪ПNТҐНЇОQТЁТЄП!spspsp НЇО╙ТП5НLО/Т²ПSТ· НLО┤ТіПYНLОЮТТspП)НLО9Т▓ПEspwpsТ⌠НLО▒pТ DЇJ=ГTаaMesa 6.0 Compiler Update11Machine Dependent RecordsMachine-dependent records are provided for situations in which the exact position of each field isimportant. In Mesa 6, you can explicitly specify word- and bit-positions in the declaration of therecord type. This form provides better documentation and usually is easier to use than theprevious, purely positional form. You should use it in preference to the old form, which remainsfor compatiblity.SyntaxVariantFieldList::=CommonPart FieldId : Access VariantPart|VariantPart|NamedFieldList|UnnamedFieldList|emptyCommonPart::=NamedFieldList , | emptyNamedFieldList::=NamedField | NamedFieldList , NamedFieldNamedField::=FieldIdList :Access TypeSpecification DefaultOptionFieldIdList::=FieldId | FieldIdList , FieldIdFieldId::=identifier | identifier ( FieldPosition )Tag::=FieldId | ...FieldPosition::=Expression : Expression .. Expression|ExpressionExamplesInterruptWord: TYPE = MACHINE DEPENDENT RECORD [ channel (0: 8..10): [0..nChannels),-- nChannels <= 8 device (0: 0..7): DeviceNumber, stopCode (0: 11..15): MACHINE DEPENDENT {finishedOK(0), errorStop(1), powerOff(3)}, command (1: 0..31): ChannelCommand];Node: TYPE = MACHINE DEPENDENT RECORD [ type (0: 0..15): TypeIndex, rator (1: 0..13): OpName, rands (1: 14..47): SELECT valence (1: 14..15): * FROM nonary => [], unary => [left (1: 16..31): POINTER TO Node], binary => [left (1: 16..31), right (1: 32..47): POINTER TO Node] ENDCASE]An identifier with an explicitly specified FieldPosition can occur only in the declaration of a fieldof a record defined to have the MACHINE DEPENDENT attribute. If the position of any field of arecord is specified, the positions of all must be. Each Expression in a FieldPosition must denote acompile-time constant, the value of which is an unsigned integer.The first expression appearing in a FieldPosition specifies the (zero-origin) record-relative index ofthe word containing the start of the field; the second and third specify the indices (zero-origin) ofthe first and last bits of the field with respect to that word. The second and third expressions mayspecify a bit offset greater than the word size if the word offset is adjusted accordingly. Similarly,the difference between the second and third expressions may exceed the word size. If the bitНЇОfЯtТНG?НЇОbТXНЇО^оpТ·ПQТ÷НЇО](Т═П)Т║П:НЇО[─ТЦП[НЇОYыТ²П!Т·П@НЇОX2ТНЇОUЇwНLОS░Н лpН'сx px px pНLО<xН лpН'сxpxНLО9 Н лpН'сx px px Н лО7СpН'сx НЇО4єwНLО2) pspsТFpТXНLО0┌wpwpН'сwpНLО.зwpwpНLО-3wp sТFpТXw pwpwpНLО+▄wpw pНLО)wpspsТFpТXНLО'iwpwpНLО%бwpwpНLО$wp spwpsНLО"spwpНLО лwpwp sТF pТXwpНLО%wpwp wp sТF pТXwpНLО}spНЇО/Т≥П+xpТ П-НЇО┤Т╠spsp Т╡П#НЇОЮТ┐П"Т└x pxp НЇО9ТПAНЇОЙТ■П$xpП5НЇОCТ⌡Т°ПEНЇО⌡Т▐П@Т░П%НЇОТТ√П2Т≈П5НЇОMТеП] >Ї=Г]∙Mesa 6.0 Compiler Update12positions are not specified, a specification of 0..n*WordSize-1 is assumed, where n is the minimumnumber of words required by the type of the field.Each field must be at least wide enough to store any value of the corresponding type. Values arestored right-justified within the fields. The current implementation of Mesa imposes the followingadditional restrictions on the sizes and alignment of fields:A field smaller than a word (16 bits) cannot cross a word boundary.Any field occupying a word or more must begin at bit zero of a word and have a size that isa multiple of the word size.A variant part may begin at any bit position (as determined by its tag field).If the sizes of all variants of a record type are less then a word, those sizes must be equal;otherwise, the size of each variant of the type must be a multiple of the word length.In the definition of a machine-dependent record type, explicitly specified field positions must notoverlap. For a variant record type, this requirement applies to the variant part (including the tag)considered in conjunction with the fields of the common part; the tag and fields particular to eachvariant must lie entirely within the variant part.The order of fields in a record type declaration need not agree with the order of those fields in therepresentation of the record; however, no gaps are permitted. For variant records, the fields of atleast one variant (including the tag field) must fill the position specified for the variant part.Dynamic Storage AllocationIn Mesa 6, you can use special constructs to describe the dynamic allocation and deallocation ofvariables. You are still responsible for managing the storage and guarding against danglingpointers; the new features handle certain routine aspects of allocation and deallocation (such ascomputing sizes), provide proper default initialization of newly allocated variables, and reduce thetotal number of LOOPHOLEs required to deal with an allocator. ZonesAllocation and deallocation are done with respect to zones. A zone need not be associated with anyspecific storage area; it is just an object characterized by procedures for allocation and deallocationas described below. The storage managed by a zone in Mesa 6 is said to be uncounted. In suchzones, object management is the responsibility of the programmer, who must explicitly program thedeallocation.To use an uncounted zone, you must provide the procedures that manage the zone and implementthe required set of operations. Many users will be able to import a suitable implementation from astandard package; the details of writing such packages are discussed below.A zone object has a value and a type. You will normally obtain a zone value by calling aprocedure exported by some package implementing zones. Typically, such a procedure constructs azone (and perhaps an initial storage pool) according to user-supplied parameters.The type of a zone value must belong to a new class of types, called zone types. Mesa 6 providestwo such types, UNCOUNTED ZONE and MDSZone. Transactions with objects having these types aregenerally in terms of LONG POINTER and POINTER values respectively (see below).ЪНЇОfЯtТНG?НЇОbpТ≥П3w pТ wpНЇО`vТП2НЇО](Т≥Т ПFНЇО[─Т≥П*Т П9НЇОYыТП=НLОW^ПCНLОTЦТ▌П4Т▐П'НLОS<ТНLОPаПNНLОNFТєП1Т╔П-НLОL·ТщП/ТчП'НЇОIPТїТ╗П]НЇОG╗Т≥Т ПGНЇОFТ■Т∙ПEНЇОDZТП2НЇОAТ▀Т▄ПOНЇО?dТ ПBТ⌡П"НЇО=╪ТьПbНЇО9 tТXНЇО6KpТ╟П9Т╠П'НЇО4єТОПSТПНЇО2ЩТбПXТцНЇО1UТєП:Т╔П*НЇО/ўТspП'НЇО,_wНЇО)pТ┘П5wpТ├П'НЇО'iТ■Т∙ПQНЇО%бТ═П:Т║wp НЇО$Т▄Т█ПIНЇО"sНЇО%Т⌠Т■ПCНЇО}Т┴П0Т┼П3НЇОжТПKНЇО┤ТжП&ТвП3НЇОЮТ▀ПIТ▄НЇО9ТПQНЇОЙТ⌠Т■ПDНЇОCТ░s pwpП/Т▒НЇО⌡ТspspП!Ъ┼ЇT=ГYЇ.Mesa 6.0 Compiler Update13Syntactically, UNCOUNTED ZONE is a type constructor. MDSZone is a predeclared identifier; you may think of it as asynonym for MDS RELATIVE UNCOUNTED ZONE (which you currently cannot write directly).You may declare variables having zone types (for which fixed initialization is recommended). Zonetypes may also be used to construct other types. In particular, you may choose to deal with pointers to zones;the NEW and FREE constructs described below provide automatic dereferencing. Allocating StorageThe operator NEW allocates new storage of a specified type, initializes it appropriately, and returns apointer to that storage. The NEW operation is considered an attribute of a zone, which must bespecified explicitly.SyntaxPrimary::=...|Variable . NEW [ TypeSpecification Initialization OptCatch ]|( Expression ) . NEW [ TypeSpecification Initialization OptCatch ]Initialization::=empty | _ InitExpr | = InitExprOptCatch::=empty | ! CatchSeriesThe value of the Variable or Expression identifies the zone to be used, either directly or after anarbitrary number of dereferencing operations. The TypeSpecification determines the type of theallocated object. If an InitExpr is provided, it must conform to the specified type and its value isused to initialize the new object; otherwise, the default value associated with that type (if any) isused. Only signals raised or propagated by the allocation procedure activate a CatchSeriesattached to NEW.The value of the Primary is a pointer to the newly allocated object. The type of that pointerdepends upon the type of the zone and the form of the Initialization. If the argument of NEW issome type T, the type of the result isLONG POINTER TO T, if the type of the zone is equivalent to UNCOUNTED ZONEPOINTER TO T, if the type of the zone is equivalent to MDSZone.If you specify fixed (=) initialization, the result is a read-only pointer with type LONG POINTER TOREADONLY T or POINTER TO READONLY T respectively.The InitExpr cannot be the special form for string body initialization ([ Expression ]). You can,however, allocate string bodies with dynamically computed sizes by using a new form ofTypeSpecification (see below). If you do so, the Initialization must be empty.Releasing StorageUncounted zones have FREE operations. When applied to an object, this operation releases thestorage allocated for that object.SyntaxStatement::=...|Variable . FREE [ Expression OptCatch ]|( Expression ) . FREE [ Expression OptCatch ]The zone used in a FREE operation is determined as described for NEW; it should be the zone fromwhich the variable was originally allocated. The argument of FREE is the address of a pointer to thevariable to be deallocated; FREE sets the pointer to NIL and deallocates the storage for the variable.НЇОfЯtТНG?НЇОbAvТ├svsvТ┤zvП6НЇО`ЮТzvsvП-НЇО]╣pТ┴П\Т┼НЇО\Т├П2vТ┤П+НЇОZfТsvsvП=pНЇОWwТXНЇОSиpТ┤spТ┬ПWНЇОR"Т╟Т╠spП>НЇОPzТНЇОMЪwНMОK└xНpН cxНОIщpН cxpТXspxpx pxpНОH6Н cx pspxpx pxpНMОE╩x НpН cxpxpxНMОC@НpН cxpx НЇО?ЯpТ√xpx pТ≈П(НЇО>JТёП-ТєxpНЇО<╒Т⌡xpПDНЇО:ШТ╗Т╘ПKНЇО9TТХП:ТИx НЇО7╛pТspНЇО4^Т©xpТюП9НЇО2ІТ²П!Т·x pspНЇО1Т wpНLО.■sТFpТXwpП+sТFНLО, pТXwpП+wpНЇО)·Т√Т≈ПAsНЇО'ВpТwpspwp НЇО$╗ТўxpП:Т╞x pНЇО#ТПBТНЇО!YxpТП!x pНЇОwТXНЇО╪pТлspП,ТмНЇОТП"НЇО wНLОxНеpН лНеОwН лxpТXsxpНеОпН лx pspx pxpНЇО │Т█Т▌spП*spНЇОзТ├П>spwpТ┤НЇО 3Т■ Т∙spspП. ТЇ Л=Г^÷Mesa 6.0 Compiler Update14Only signals raised or propagated by the deallocation procedure activate a CatchSeries on a FREE.Implementing Uncounted ZonesThis section describes the assumptions currently made by the compiler about the user-suppliedimplementations of uncounted zones. These assumptions are compatible with the style of "object-oriented" programming that has proven successful in a number of applications. You need to readthis section only if you are designing the interface between a storage management package and thezone features of the language.An uncounted zone dealing with LONG POINTER values is represented by a two word value, whichthe compiler assumes to be a long pointer compatible with the following skeletal structure:UncountedZoneRep: TYPE = LONG POINTER TO MACHINE DEPENDENT RECORD [ procs (0:0..31): LONG POINTER TO MACHINE DEPENDENT RECORD [ alloc (0): PROC [zone: UncountedZoneRep, size: CARDINAL] RETURNS [LONG POINTER], dealloc (1): PROC [zone: UncountedZoneRep, object: LONG POINTER] -- possibly followed by other fields-- ], data (2:0..31): LONG POINTER-- optional, see below -- possibly followed by other fields-- ];If z is an uncounted zone, the code generated for p _ z.NEW[T] is equivalent top _ z^.procs^.alloc[z, SIZE[T]]and the code generated by z.FREE[@p] is equivalent to{temp: LONG POINTER _ p; p _ NIL; z^.procs^.dealloc[z, temp]}.Within this framework, you may design a representation of zone objects appropriate for yourstorage manager. In general, you should create an instance of a finger (the record with fields procsand data) for each instance of a zone. The record designated by the procs pointer can be shared byall zones with the same implementation. The data pointer normally designates a particular zoneand/or the state information characterizing that zone. Note that the compiler makes no assumptionsabout the designated object and does not generate any code referencing the data field. The extralevel of indirection provided by that field is not obligatory; you may replace it with stateinformation contained directly in the finger (but following the procs field).The compiler assumes a similar (but single word) representation for an MDSZone value; theskeletal structure is as follows: MDSZoneRep: TYPE = POINTER TO MACHINE DEPENDENT RECORD [ procs (0:0..15): POINTER TO MACHINE DEPENDENT RECORD [ alloc (0): PROC [zone: MDSZoneRep, size: CARDINAL] RETURNS [POINTER], dealloc (1): PROC [zone: MDSZoneRep, object: POINTER] -- possibly followed by other fields-- ], data (1:0..15): POINTER-- optional -- possibly followed by other fields-- ];НЇОfЯtТНG?НЇОbpТ⌠ПKx pТ■spНЇО^оwТXНЇО[─pТлТмПGНЇОYыТ°ПTТ²НЇОX2Т≥П0Т П/НЇОV┼Т⌠Т■ПIНЇОTЦТНЇОQ■Т║spТ╒П1НЇОOМТУТЖПDНLОMrwpТXspsТFП$pТXНLОKкwpsТFП*НLОJ#pТXw pspwpwpwpspspsТFpНLОH|ТXwpspwpwpwpsТFpТXspНLОFуwpП)НLОE-wpsТFН.зpТXНLОC├П-НЇО@7wpП.wpwpspwpНLО=╪wpwpwpwpwpspwpНЇО;AwpspwpНLО8фwpsТFpТXwpwpspwpwpwpwpwpНЇО5xТзТшП=НЇО3пТ▐ПAwpТ░wНЇО2)pТ┘wpТ├ПГU■!Mesa 6.0 Compiler Update16SeqTag ::=identifier : Access BoundsType |COMPUTED BoundsTypeBoundsType ::=IndexTypeTypeSpecification ::=. . . |TypeIdentifier [ Expression ]The TypeSpecification in VariantPart establishes the type of the sequence elements. TheBoundsType appearing in the SeqTag determines the type of the indices used to select from thoseelements. It is also the type of a tag value that is associated with each particular sequence object toencode the length of that object. For any such object, all valid indices are smaller than the value ofthe tag. If T is the BoundsType, the sequence type is effectively a union of array types with theindex typesT[FIRST[T] .. FIRST[T]), T[FIRST[T] .. SUCC[FIRST[T]]), ... T[FIRST[T] .. LAST[T])and a sequence with tag value v has index type T[FIRST[T]..v). Note that the smallest interval in thisunion is empty.If you use the first form of SeqTag, the value of the tag is stored with the sequence and isavailable for subscript checking. In the form using COMPUTED, no such value is stored, and nobounds checking is possible.Examples:StackRep: TYPE = RECORD [ top: INTEGER _ 1, item: SEQUENCE size: [0..LAST[INTEGER]] OF T]Number: TYPE = RECORD [ sign: {plus, minus}, magnitude: SELECT kind: * FROM short => [val: [0..1000)], long => [val: LONG CARDINAL], extended => [val: SEQUENCE length: CARDINAL OF CARDINAL] ENDCASE]WordSeq: TYPE = RECORD [SEQUENCE COMPUTED CARDINAL OF Word]The final example illustrates the recommended method for imposing an indexable structure on raw storage.If S is a type containing a sequence field, and n is an expression with a type conforming toCARDINAL, both S and S[n] are TypeSpecifications. They denote different types, however, and thevalid uses of those types are different, as described below.MACHINE DEPENDENT SequencesYou may declare a field with a sequence type within a MACHINE DEPENDENT record. Such a fieldmust come last, both in the declaration and in the layout of the record, and the total length of arecord with a zero-component sequence part must be a multiple of the word length. If youexplicitly specify bit positions, the size of the sequence field also must describe a zero-lengthsequence; i.e., it must account for just the space occupied by the tag field (if any). ЪНЇОfЯpТНG?НLОbuНеqТXН лu ququ НеО`vquН лtqu НLО]Ш НеqН лuНLОYыqН лuНеОX2quН л qu qНЇОTЦТЩuqu qТЧНЇОScardinality(Ti), and you have requested bounds checking.If FIRST[Ti] = 0, SUCCn[FIRST[Ti]] is just n, i.e., the interpretation of the tag is most intuitive if Ti isa zero-origin subrange. Usually you will specify a BoundsType (e.g., CARDINAL) with a range thatcomfortably exceeds the maximum expected sequence length. If, however, some maximum lengthN is important to you, you should consider using [0..N] as the BoundsType; then the value of thetag field in a sequence of length n (n < N) is just n and the valid indices are in the interval [0..n).НЇОfЯpТНG?НЇОbqНLО^оrqТXtqtТFqТXНLО](rqtqНLО[─rqtqrqtТFqТXrqНLОX2rqtqtТFqТXНLОV┼rqtqНLОTЦrqtТFqТXtТFqТXtТF qНЇОQ■rТXНЇОNFqТ▒rqП&Т▓rqrqНЇОL·Т─П3Т│rqrq НЇОJВТ⌡tqrqТ°П*НЇОIPТ├П'Т┤П7tqНЇОG╗Т░П)Т▒tqП"rqrqНЇОFТП;НЇОB╡Т÷Т═tqrqrqtqП'НЇОAТrqrqП!НЇО=╪Т▒rqtqrqrqt qrqТ▓tqrq НЇО<Т■rqП0tqrqrqНЇО:nТ rqП+НLО7СТXПIНLО5xП*tО6sО5xqtqrq rqНLО2ЩП8НЇО/ўТ▌П^Т▐rqНЇО.Т╛tqТґПOНЇО,_Т└П4Т┘П2НЇО*╦Т²ПOТ· tНЇО)qТ НЇО%бНLО#GrqТXtТFqТXrqrqtqrqН.зrqrqНLО лrqtТF qТXrqtqrqrqrqrqrqtqНLОQrqtТF qТXrqrqtqrqrqНЇОТ⌠ rqПRНЇО[tqТ·u qrОнsО[quqТ÷НЇО'Т°tОЄsО'qtqrО sО'qП@rО sО'q rqvНЇО\r qrОоsО\qТrqП$НЇО1Т┼tqrОєsО1qtОЎsО1qtqrОєsО1q rqП;rОєsО1qТ▀НЇОfТ√Т≈u qtqНЇО©Т÷ПTТ═НЇО rqТ⌠П4rqu qТ■НЇОpТ█Т▌rqrqvqrq rqП/rq▌Ї)=Г\БMesa 6.0 Compiler Update18Operations on SequencesYou can use a sequence-containing type S only as the argument of the type constructor POINTER TO.Note that the type of z.NEW[S[n]] is POINTER TO S (not POINTER TO S[n]). If the type of an objectis S, the operations defined upon that object areordinary access to fields in the common partreadonly access to the tag field (if not COMPUTED)indexing of the sequence fieldconstructing a descriptor for the components of the sequence field (if not COMPUTED).There are no other operations upon either type S or the sequence type embedded within S. Inparticular, you cannot assign or compare sequences or sequence-containing records (except byexplicitly programming operations on the components).Indexing: You may use indexing to select elements of the sequence-containing field of a record byusing ordinary subscript notation, e.g., s.seq[i]. The type of the indexing expression i must conformto the BoundsType appearing in the declaration of the sequence field and must be less than thevalue of the tag, as described above. The result designates a variable with the type of the sequenceelements. A bounds fault occurs if the index is out of range, the sequence is not COMPUTED, andyou have requested bounds checking.By convention, the indexing operation upon sequences extends to records containing sequence-valued fields. Thus you need not supply the field name in the indexing operation. Note too thatboth indexing and field selection provide automatic dereferencing.Examples:ps^.item[ps.top] ps.item[ps.top] ps[ps.top] -- all equivalentDescriptors: You may apply the DESCRIPTOR operator to the sequence field of a record; the result isa descriptor for the elements of that field. The resulting value has a descriptor type with index andcomponent types and PACKED attribute equal to the corresponding attributes of the sequence type.By extension, DESCRIPTOR may be applied to a sequence-containing record to obtain a descriptor forthe sequence part. The DESCRIPTOR operator does not automatically dereference its argument.You cannot use the single-argument form of the DESCRIPTOR operator if the sequence is COMPUTED.The multiple-argument form remains available for constructing such descriptor values explicitly (andwithout type checking).In any new programming, you should consider the following style recommendation: use sequence-containing types forallocation of arrays with dynamically computed size; use array descriptor types only for parameter passing.Examples:DESCRIPTOR[pn^] DESCRIPTOR[pn.sons] -- equivalentString Bodies and TEXTThe type StringBody provided by previous versions of Mesa illustrates the intended properties anduses of sequences. For compatibility reasons, it has not been redefined as a sequence; thedeclarations of the types STRING and StringBody remain as follows:ЪНЇОfЯpТНG?НЇОbrНЇО^оqТ┌П'rqТ┐П.t qНЇО](Т┬rqtqrqrqt qrqt qrqrqТ┴НЇО[─ТrqП-НLОYТXП,НLОV┼П)tqНLОTНLОQ■ПKtqНЇОNFТ╞П/rqП&rqТ╟НЇОL·ТБП2ТЦП*НЇОJВТП5НЇОG╗rqТ■Т∙ПLНЇОFТ▄П)rqrqrqТ█П&rqНЇОDZТіu qПMНЇОB╡Т┴Т┼ПTНЇОAТ·ПKТ÷tqrНЇО?dqТП#НЇО<ТпП4ТяП(НЇО:nТ≤П>Т≥П#НЇО8фТПBНЇО5xНґО2ЩrqrqrqrqТXrqrqrqrqrqrqrqНЇО/ўrqТ├Т┤ t qП:НЇО.Т┬ПfНЇО,_Т²tqП0Т·НЇО*╦Т┌ t qТ┐ПCНЇО)Тяt qТрП1НЇО%бТ┬П/t qtqНЇО$Т┐П=Т└П'НЇО"sТНЇОHsТ╚ПqНЇОГТПkНЇО╪qНґОAt qrqТXt qrqrqНЇОpТНЇОпqТ≥r qПJТ НЇО)ТКПWТЛНЇО │Тtqr q2Ї :>ГZя`Mesa 6.0 Compiler Update19STRING: TYPE = POINTER TO StringBody;StringBody: TYPE = MACHINE DEPENDENT RECORD [ length (0): CARDINAL _ 0, maxlength (1): --READONLY-- CARDINAL, text (2): PACKED ARRAY [0..0) OF CHARACTER]The operations upon sequence-containing types have, however, been extended to StringBody so thatits operational behavior is similar. In these extensions, the common part of the record consists ofthe field length, maxlength serves as the tag, and text is the collection of indexable components(packed characters). Thus z.NEW[StringBody[n]] creates a StringBody with maxlength = n andreturns a STRING; if s is a STRING, s[i] is an indexing operation upon the text of s, DESCRIPTOR[s^]creates a DESCRIPTOR FOR PACKED ARRAY OF CHARACTER, etc.There are two anomalies arising from the actual declaration of StringBody: s.text[i] never uses bounds checking,and DESCRIPTOR[s.text] produces a descriptor for an array of length 0. Use s[i] and DESCRIPTOR[s^] instead.Type TEXTThe type TEXT, which describes a structure similar to a StringBody as a true sequence, is predeclaredin Mesa 6. Its components length and maxLength are declared to have a type compatible witheither signed or unsigned numbers (but with only half the range of INTEGER or CARDINAL).TEXT: TYPE = MACHINE DEPENDENT RECORD [ length (0): [0..LAST[INTEGER]] _ 0, text (1): PACKED SEQUENCE maxLength (1): [0..LAST[INTEGER]] OF CHARACTER]Exported TypesAn exported type is a type designated by an identifier that is declared in an interface andsubsequently bound to some concrete type supplied by a module exporting that interface. This isanalogous to the current treatment of procedures in interfaces, where the implementations ofprocedures (i.e., the procedure bodies) do not appear in the interface but are defined separately.The advantages are twofold:The internal structure of the type is guaranteed to be invisible to clients of the interface.There are no compilation dependencies between the definition of the concrete type and theinterface module. The definition of that type can be changed and/or recompiled at any time(perhaps subject to a size constraint; see below) without requiring recompilation of either theinterface or any client of the interface.The uses of an exported type are the same as those of any other type, e.g, to construct other types.The value provided by the interface is constant but has no accessible internal structure. In Mesa 6,there are two other important differences between exported procedures and exported types.The first is a restriction necessary to ensure type safety across module boundaries. Differentexporters of an interface can supply different implementations of any particular procedure in thatinterface. In Mesa 6, this is not true for exported types; all exporters of a particular type within aconfiguration must supply the same concrete type, which is called the standard implementation ofthat exported type. Because of this restriction, clients can safely interassign values with exportedtype T, no matter how obtained. In addition, any exporter of T may convert a value of type T to avalue of the concrete type it uses to represent T and conversely.The second difference is that it is not necessary to import an interface to access an exported typedefined within it or to distinguish among values of such a type coming from different importedНЇОfЯpТНG?НLОbtqТXtqtТFqТXr НLО_ё qtqtТFqТXНLО]ШrqtqНLО\TrqtТFqНLОZґТXrqtТFqТXtqtqНЇОW^Т┬П<Т┴r qНЇОUЇТ·П:Т÷П*НЇОTТЇТ╦rqrqrqП*НЇОRhТтТуrqtqr qrqr qrqrqНЇОPаТ° tqrqtqrqrqТ²rqt qrqНЇОOТ tП(qНLОLбsТ║П?w sТ╒wswswswsНLОKaТ▌t swswsП.Т▐wswst sws НЇОH6rТtНЇОDГqТ─tqТ│r qП#НЇОC@Т╦rqrqТ╧НЇОA≤ТЯТРП6tqtqНLО?tqТXtqtТFqТXНLО=vrq tqtqНLО;оrqtТFqТXrq tqtqtqtqНЇО7╛p НЇО4^qТПrq ТЯПAНЇО2ІТёrq ТєП*НЇО1ТФП0ТГП,НЇО/hТ╡ПNТЁНЇО-юТНLО+EТXП]НLО(йТїП-Т╗П,НLО'#Т▐Т░ПIНLО%|Т⌠ПCТ■НLО#тТП)НЇО ├Т▌Т▐ПMНЇОчТ▀П7Т▄П.НЇО7ТПYНЇОХТз ТшПQНЇОAТіПPТїНЇО Т⌡Т°rП#qП-НЇОРТ╛П:ТґrqНЇОKТ╛П1ТґП4НЇОєТ├rqП8rqТ┤rqНЇОЭТП0rqНЇОўТ║П;Т╒П(НЇОТ╣П3ТІП+ >Ї ©>Г]LяMesa 6.0 Compiler Update20instances. This is another consequence of the fact that, in Mesa 6, all interfaces must reference thestandard implementation of the exported type.Interface ModulesAn exported type is declared in an interface (DEFINITIONS) module using one of the following twoforms:T: TYPE;T: TYPE [ Expression ];The first of these introduces a type T, no properties of which are known in the interface or to anyclient of the interface. In particular, the size of T is not known; this is adequate (and desirable) ifthe interface and clients deal only with values of type POINTER TO T.The second form specifies the size of the values used in the representation of the type. The valueof Expression, which must denote a compile-time constant with an unsigned integer value, givesthis size in units of machine words. Supplying the size of an exported type is a shorthand forexporting a set of fundamental operations (creation, _ , =, and #) upon that type. In Mesa 6, theeventual concrete type must supply the standard implementations of these operations, which aredefined as follows:creationallocate the specified number of words, with no initialization_copy an uninterpreted bit string=, #compare uninterpreted bit stringsNote that a type with non-NULL default value does not have the standard creation operation. Such types cannot beexported with known size. You should therefore consider writing your interfaces in terms of POINTER TO T, where Tis a completely opaque exported type and not subject to these restrictions.Client ModulesA client has no knowledge of the type T beyond those properties specified in the interface. If thesize is not specified there, no operations on T are permitted. If the size is available from theinterface, SIZE[T] is legal; also declaration of variables (including record fields and arraycomponents) and the operations _, =, # are defined for type T.Implementation ModulesAn implementor exports a type T to some interface Defs by declaring the type with the requiredidentifier, the PUBLIC attribute, and a value that is the concrete type; e.g., inT: PUBLIC TYPE = S;S specifies the concrete type. If the size of T appears in the interface, the definition of T in theexporter must specify a type with that size and with the standard fundamental operations (thecompiler checks this).Within an exporter, Defs.T and T conform freely and are assignment compatible. Otherwise, Defs.Tis treated opaquely there and is not equivalent to T (except for the purpose of checking exports).You should therefore attempt to write an exporting module entirely in terms of concrete types.Consider the following example:ЪНЇОfЯpТНG?НЇОbqТ▌ПbТ▐НЇО`vТП-НЇО](rНЇОYыqТ═П"Т║t qП'НЇОX2НLОUЇrqТtqНLОTrqtqru rqНЇОQ■Т⌠Т■rqrqП9НЇОOМТ▓П5rqТ⌠НЇОNFТП8t qrqНЇОKкТ∙П8Т√П+НЇОJ#Т╛u qП<ТґНЇОH|Т╦Т╧ПSНЇОFуТ┤ПSТ┬НЇОE-ТгП&ТхrqНЇОC├ТНLОAНеТXП>НLО>░НеНLО<НеП!НЇО8ЙsТєtsТ╔П3НЇО7┴Т▌Т▐ПDt swswНЇО6(sТПKНЇО2Щr НЇО/ўqТ■Т∙rqП<НЇО.ТаП.rqТбП#НЇО,_Т& tqrqПFТ'НЇО*╦ТПГW░Т∙rqТ√ПPНЇО<ИrqrqТ▐rqrqТ░rqrqrqНЇО;AТ┬ tqП<Т┴ НЇО9 rqТ°Т²ПKНЇО7СТП+НЇО4єrНЇО1UqТ╣П1rqП&ТІНЇО/ўТ·rqП-Т÷НЇО.Т├П1rqТ┤НЇО,_rqТПHНЇО(=pТXНЇО$НqТ░ПBtqТ▒ НЇО#GТ╔П-ТіП.tНЇО!═qТНЇО%rНLО╙uНеqН лtuТX quqtquНеОН лtu qu quqtquНLО┤ НеqН лtu qu qu НеОЮН лtu qu qu qu НЇО▒qТ uqu qТ⌡uqНЇОЙТ√П:tqТ≈ НЇОCuqТяuqu q ТрuqНЇО⌡Т▐П5Т░uquq dЇT>ГYЇкMesa 6.0 Compiler Update22Extended NILIn Mesa 6, null values are available for all address-containing types. An address-containing type isone constructed using POINTER, DESCRIPTOR, PROCEDURE, PROGRAM, SIGNAL, ERROR, PROCESS,PORT, ZONE or a LONG or subrange form of one of the preceding. The built-in type STRING isaddress-containing. A relative pointer or relative descriptor type is not considered to be address-containing in Mesa6.Null values are denoted as follows:If T designates any address-containing type, NIL[T] denotes the corresponding null value.Whenever T is implied by context, NIL abbreviates NIL[T].If T is not implied by context, NIL means NIL[POINTER TO UNSPECIFIED] and thus continues tomatch any POINTER or LONG POINTER type.A fault will occur if you attempt to dereference a null value and have requested NIL checking; afault will occur unconditionally if you attempt to transfer control through a null value.Reject StatementWithin a catch phrase, you can use the statement REJECT to explicitly reject a signal, i.e., toterminate execution of that catch phrase and propagate the signal to the enclosing one. (Note thateach catch phrase is currently terminated by an implicit REJECT.)Process ExtensionsAborting a process now raises the predeclared signal ABORTED. The predeclared typesMONITORLOCK and CONDITION are now defined with default initialization. The only client-visiblefield is timeout in CONDITION; its default initial value is 100 ticks.Restrictions on AssignmentThe assignment operations defined upon certain types have been restricted so that variables of thosetypes can be initialized (either explicitly or by default) when they are created but cannotsubsequently be updated. A variable is considered to be created at its point of declaration or, fordynamically allocated objects, by the corresponding NEW operation.In Mesa 6, the following types have restricted assignment operations:MONITORLOCKCONDITIONany type constructed using PORTany type constructed using SEQUENCEany type constructed using ARRAY in which the component type has a restricted assignmentoperation.any type constructed using RECORD in which one of the field types has a restricted assignmentoperation.Note that the restrictions upon assignment for a type do not impose restrictions upon assignment tocomponent types. Thus selective updating of fields of a variable may be possible even when theЪНЇОfЯpТНG?НЇОbТXНЇО^оqТ⌠ПbТ■НЇО](ТЛtqТМt qtqtqtqtqtqНЇО[─tqТ╧tqТ╨tqП>tqНЇОYыТ▐sП)Т░П8НЇОXUНЇОU*qТXП#НLОR╞rqП)tqrqП'НLОP4rqtqtqrqНLОM╧Т∙rqtqТ√tqtqНLОLТ tqtqНЇОHцТ╛П7ТґrqtqНЇОGТПYНЇОBЫpТXНЇО?╙qТыП1tqП(НЇО>Т⌠Т■ПPНЇО<\ТП9tqНЇО89pТXНЇО4КqТ;П5tqТ<НЇО3Ct qТ╨tqП7Т╩НЇО1°ТrqtqП)НЇО-zpНЇО*+qТ┘П[Т├НЇО(└ТТПCНЇО&эТ⌡ПdНЇО%5ТП4tq НЇО!ФПEНLОkt НLОПНLОuqТXtНLОЗqtНLОqТ╙tqТ╚П+НLОь НLО]Т├tqП1Т┤ НLОІ НЇО ;Т┴Т┼ПZНЇО⌠ТіТїП? hЇL=Г\©8Mesa 6.0 Compiler Update23entire variable cannot be updated; e.g., the timeout field of a CONDITION variable can be updated byordinary assignment. Also, you may apply the operator @ to obtain the address of the entirevariable in such a situation.Operational ChangesUser InterfaceThe standard Mesa 6 Compiler reads commands only from the executive's command line; it nolonger supports interactive input. During compilation, the display and keyboard are disabled. Thecursor provides a limited amount of feedback; it moves down the screen to indicate progressthrough a sequence of commands and to the right as errors are detected. At the end ofcompilation, the message "Type Key" is displayed in a flashing cursor if there are errors and youhave requested the compiler to pause. Typing Shift-Swat aborts the Executive's currentcommand sequence; Ctrl-Swat invokes the Mesa Debugger; any other character causes normalexit from the compiler.A summary of compilation commands is written on the file Compiler.log (formerly,Mesa.typescript).Command Line ArgumentsThe Mesa 6 Compiler allows you to control the association between modules and file names at thetime you invoke the compiler. The compiler accepts a series of commands, each of which has theformoutputFile _ inputFile[id1: file1, ..., idn: filen]/switchesOnly inputFile is mandatory; it names the file containing the source text of the module to becompiled, and its default extension is .mesa. Any warning or error messages are written on thefile outputRoot.errlog, where outputRoot is the string obtained by deleting any extensionfrom outputFile, if given, otherwise from inputFile. If there are no errors or warnings, anyexisting error log with the same name is deleted at the end of the compilation.If a list of keyword arguments appears between brackets, each item establishes a correspondencebetween the name idi of an included module, as it appears in the DIRECTORY of the sourceprogram, and a file with name filei; the default extension for such file names is .bcd. (If thename of an included module is not mentioned on the command line, its file name is computedfrom information in the DIRECTORY statement; see above).The optional switches are a sequence of zero or more letters. Each letter is interpreted as aseparate switch designator, and each may optionally be preceded by - or ~ to invert the sense ofthe switch.If outputFile (and _) are omitted, the object code and symbol tables are written on the fileinputRoot.bcd, where inputRoot is inputFile with any extension deleted. Otherwise codeand symbols are written on outputFile, for which a default extension of .bcd is supplied. Ifthe compiler detects any errors, the output file is not written and any existing file with the samename is deleted.The compiler accepts a sequence of one or more commands from the executive's command line(through the file Com.cm). Commands are separated by semicolons, but you may omit a semicolonНЇОfЯpТНG?НЇОbqТ┬П-rqtqТ┴НЇО`vТдПBТеНЇО^оТНЇОY⌠xТiНЇОUppТX НЇОR"qТ╧Т╨ПFНЇОPzТ▐ПCТ░НЇОNсТыПFТзНЇОM,ТТТУПMНЇОK└Т÷П&Т═П;НЇОIщТВП%ТЬy qНЇОH6Т╛yqТґП"НЇОF▌ТНЇОC@Т:Т;П0yq НЇОA≤yquНЇО=vpТXНЇО:'qТ▓Т⌠ПEНЇО8─Т≈Т≤ПBНЇО6ыНLО4^yТвО3яtО4^yО3яtО4^yО3яtО4^yО3яtО4^y НЇО12qТєyqТ╔П8НЇО/▀П'yqТіП3НЇО-ДТ╙yqy qТ╚П1НЇО,<Т∙y qТ√yqП*НЇО*∙ТПOНЇО'FТЁТЄПSНЇО%÷ТыТзyО%tО%÷qП-tq НЇО#тТ╒yО#GtО#тqТёyq НЇО" Т╣ТІПGНЇО bТtqНЇОТ╣ТІyqПIНЇОlТ╒ПCyqyqНЇОеТ НЇОvТ╧y qТ╨yqПHНЇОоyqТ∙yqyqТ√П,НЇО(Тє Т╔y qП#yqНЇО─Т╗П3Т╘П0НЇОыТНЇО┼ТЇП.Т╦П+НЇО ЦТ┘yqТ├П:▌Ї °=Г]osMesa 6.0 Compiler Update24between any two successive identifiers (file names or switches), or between a ] and an identifier (butnot between an identifier and a /). Note that any required semicolon in an Alto Executivecommand must be quoted.You can set global switches by a command with an empty file name. In the form /switches,each letter designates a different switch. Unless a command to change the global switch settingscomes first in the sequence of commands, you must separate it from the preceding command by anexplicit semicolon. Note that the form switch/c is no longer available for setting global switches.SwitchesThe following compilation options have been added:SwitchOption Controlled fimplementation of floating-point operations ltreatment of long pointers ywarning on runtime callsIf the f switch is set, the compiler generates byte code instructions for floating-point operations(these require microcode support); otherwise, it generates calls through the system dispatch vector(SD) to software routines implementing such operations. If the a and l switches are both set, thecompiler generates code using an variant of the Alto Mesa instruction set that implements longpointer accesses to a virtual memory larger than 64K (code generated using the l switch cannot beexecuted on an Alto, even if long pointers are not used). If you specify -a, the l switch is ignored.The y switch indicates that a warning message should be issued whenever the compiler generatescode to invoke a runtime procedure (including some "instructions" which are actually implementedin software).The default settings for these switches are f, -l and -y.Distribution: Mesa Users Mesa Group SD SupportЪНЇОfЯpТНG?НЇОbqТ└ПMТ┘НЇО`vТыyqП9НЇО^оТНЇО[─Т╘Т╙ПHyqНЇОYыТ╛П"ТґП?НЇОX2Т▀ПPТ▄ НЇОV┼ТstsП4НЇОRhpНЇОOqТXП2НґОL·rН лrНґОJ#qyН лqН,ОIлЧyОJ#НґОG╗yН лqН(\ОGQЧcОG╗НґОE-yН лqНЇОB╡Т╦yqТ╧ПHНЇОAТ╔П@ТіП#НЇО?dТ√П@yqТ≈yqНЇО=╪ТЎП/Т©П/НЇО<Т░Т▒ПГAИCopyright c Xerox Corporation 1980Inter-Office MemorandumToMesa UsersDateOctober 27, 1980FromBrian Lewis, Ed SatterthwaiteLocationPalo AltoSubjectMesa 6.0 Binder UpdateOrganizationSDD/SS/MesaXEROX Filed on: [Iris]Doc>Binder60.bravo (and .press)This memo describes changes to the C/Mesa language and the Binder that have been made sincethe release of Mesa 5.0 (April 9, 1979).Definitions of syntactic phrase classes used but not defined in this document come from the MesaLanguage Manual, Version 5.0, Section 7.7.CompatibilityBecause of changes in BCD formats, you must rebind all your existing Mesa configurations afterobtaining recompiled versions of their components. There is one potential incompatibility:Some of the quoted file names that appear in DIRECTORY clauses have differentinterpretations. Text inside angle brackets is no longer ignored; it is treated as the name of alocal subdirectory (but we do not recommend using local subdirectories for Mesa programs atthe present time).A number of bugs have been fixed. As usual, the list of Binder-related change requests closed byMesa 6.0 will appear separately as part of the Software Release Description. The most notableinvolvecorrectly checking the types of interfaces when positional notation is used,proper treatment of named imports or exports of a configuration,proper identification of object files that have been renamed.Because of bug fixes, the Binder may reject previously acceptable configuration descriptions or mayissue new warning messages. A number of error or warning messages now use symbolic nameswhenever the corresponding symbol tables are available.ЪН!вОpТX qpН]Оg~rТiНІОcsН]pТX Н-єsН7BpНІО]ШsН]pН-єsН7BpНІОYsН]tН-єsН7Bp НЭОSЛupНЇОN#sТFП5НЇОG╗pТ╒П:ТёП!НЇОFТП(НЇОB╡Т⌡П[Т°vНЇОAТp НЇО;оrНЇО8─pТ╨spП"Т╩П#НЇО6ыТП[НLО4^ТGП-spТHНLО2ІТ▀ПSТ▄ НLО1Т█П[НLО/hТНЇО,Т≈Т≤ПLНЇО*rТхТиПIНЇО(йНLО&OТПLНLО#тП@НLО!YП=НЇОТ█Т▌ПJНЇОcТІПBТЇНЇО╪ТП7pЭр=Гd хMesa 6.0 Binder Update2New Language FeaturesBracket SymbolsThe bracket pair { } can be used in place of BEGIN END.SyntaxCBody::=BEGIN CStatementSeries END|{ CStatementSeries }Multiple Control ModulesYou can now specify an ordered list of control modules for any configuration.SyntaxControlClause::=CONTROL IdList|emptyIdList::=identifier | IdList , identifierWhen a (sub)configuration is started, either explicitly or as the result of a start trap (see the MesaLanguage Manual, Version 5.0, Section 7.8.4), each of the modules named in the ControlClause isstarted in order.Note that, if there are calls from a control module to one of its successors in the list, the order ofstarting will not necessarily follow the order of the ControlClause. In starting a configuration, anycontrol modules that have already been started are skipped.Operational ChangesThe Binder is now available only as a .bcd file; you must have Mesa.image to run it. Whencompressing symbols, SymbolCompressor.bcd must be loaded first; see the description of the /x switch below.User InterfaceThe Binder now reads commands only from the Alto Executive's command line; it no longersupports interactive input. At the start of the first binding, the message "Bind" is displayed in thecursor. If there are any warnings, "Warning" is displayed, and if there are errors "Errors" is shown.At the end of binding, the message "Type Key" is displayed in a flashing cursor if there are errorsand you have requested the Binder to pause. Typing Shift-Swat aborts the executive's currentcommand sequence; Ctrl-Swat invokes the Mesa Debugger; any other character causes normalexit from the Binder.A summary of binder commands is written on the file Binder.log (formerlyMesa.typescript).НЇОfЯtТНGОНЇОaвrТiНЇО]╣tТXНЇОZfpП/spspНЇОWКvНLОUpwН лpН'сswsН лОSиwН'сpwpНЇОOїtНЇОLXpПMНЇОIщvНLОGbwН лpН'сswН лОE╩Н'сНLОC@Н лpН'сwpw НЇО?ЯpТ⌡ПbvНЇО>JТ■pП.Т∙wpНЇО<╒ТНЇО9TТ≤П=Т≥П)НЇО7╛Т▄П5Т█wpП#НЇО6ТП;НЇО0хrТiНЇО-zpТ╟Т╠xpx pyНЇО+рТщsyП-Тчsy НЇО'╟tТX НЇО$apТсТтП:НЇО"╨Т⌠ПRТ■НЇО!Т│Т┌ПUНЇОkТ▐Т░ПMНЇОдТ·Т÷x pНЇОТ╛xpТґП"НЇОuТНЇО'ТЁП4x p НЇОxpwЪжЇ8>ГRсЗMesa 6.0 Binder Update3CommandsThe Mesa 6.0 Binder allows you to control the names and contents of various output files when youinvoke it; it accepts a series of commands, each of which usually has one of the following forms:inputFile/switchesoutputFile _ inputFile/switches[key1: file1, ... keym: filem] _ inputFile/switches(It is also possible to control the association between included modules and configurations and theirfile names; this is described below.) In the last form, key is one of bcd, code, or symbols.The string inputFile names the file containing the source text of the configuration description,and its default extension is .config.There is a principal output file, the name of which is determined as follows:If you use the first command form, it is inputRoot.bcd, where inputRoot is the stringobtained by deleting any extension from inputFile.If you use the second form, it is outputFile, with default extension .bcd.If you use the third form and keyi is bcd, it is filei, with default extension .bcd;otherwise, it is obtained as described for the first form.If the Binder detects any errors, the principal output file is not written, and any existing file withthe same name is deleted.You may also request that the code and/or symbols of the constituent modules be copied to anoutput file, as follows:You request copying of code by specifying the /c switch or by using the third command formwith keyword code. Code is copied to the principal output file unless you use the third formand keyi is code, in which case the code is copied to a file named filei, with defaultextension .code.You request copying of symbols by specifying the /s or /x switch or by using the thirdcommand form with keyword symbols. Symbols are copied to the fileinputRoot.symbols unless you use the third form and keyi is symbols, in which casethey are copied to a file named filei, with default extension .symbols. Compressedsymbols are copied if the /x switch is specified.Any warning or error messages are written on the file outputRoot.errlog, where outputRootis the string obtained by deleting any extension from the name of the principal output file. If thereare no errors or warnings, any existing error log with the same name is deleted at the end of thebind.When more than one Binder command is given on the command line, the commands must beseparated by semicolons. However, you may omit a semicolon between any two successiveidentifiers (file names or switches), or between a ] and an identifier (but not between an identifierand a /). Note that any required semicolon in an Alto Executive command must be quoted.НЇОfЯtТНGОНЇОbНЇО^оpТ┐Т└ПCНЇО](Т╒ПZТёНLОZґxНLОX2ТвНLОUЇОU*sОUЇxОU*sОUЇxОU*sОUЇwxОU*sОUЇxНЇОR▀pТ┴П_Т┼НЇОPДТЄП2Т╣xp xpxpxpНЇОM∙Т╔ xpТіП.НЇОKНТxpНЇОH÷ vpП9НLОF$Т║П)xpxpТ╒ НLОD}ТП(xpНLОBП"x pxpНLО?┤ТЮТАxО>ЗsО?┤pxpxО>ЗsО?┤pxpНLО=╪ТП:НЇО:nТ═П\Т║ НЇО8фТНЇО5xТ╠Т╡П?НЇО3пТНLО1UТ─П-Т│xpvpНLО/ўТ┌xpПGТ┐НLО.ТаxО-zsО.pxp ТбП)xО-zsО.p НLО,<Т xpНLО)аТҐП1xpxpvpНLО(Т╪xp ТҐНLО&sxpТїТ╗xО%ФsО&spxpНLО$╗ТтТуxО$sО$╗pxpНLО"щТxpНЇО▐Т┤П,Т┬ xpx НЇОГpТ├П\Т┤ НЇО@Т║ПRТ╒НЇО≥НЇОJТаТбПKНЇОёТТПKТУ НЇОШТ ПFТ⌡НЇОTТиТйxpПQЪ BЇ =ГUЧqMesa 6.0 Binder Update4SwitchesThe optional switches are a sequence of zero or more letters. Each letter is interpreted as aseparate switch designator, and each may optionally be preceded by - or ~ to invert the sense ofthe switch.The Binder recognizes the switches:/c- copy code/s- copy symbols/x- copy compressed symbols/p- pause after binding if there are errors or warnings/r- run the specified .image or .run file/g- (has no effect; retained for compatibility with Mesa 5)The Mesa 5 Binder switch /o (output file) is no longer available.In earlier versions of the Binder, copying symbols was an error if not all of the symbol files wereavailable at bind time. The Binder now copies all symbols that it can find, leaves the symbol tablereferences for the other modules in the original (unavailable) files, and issues a warning.The switches /c and /s are interpreted differently in Mesa 6 than they were in Mesa 5. Thefollowing table outlines these changes. Mesa 6Mesa 5meaningfile/cfile/ccode to file.bcdfile/csfile/c file/scode to file.bcd;symbols to file.symbols[symbols: file.bcd] _ file/cfile/cscode and symbols to file.bcdNote that file/cs has quite a different meaning in Mesa 6 than before. Also, the common Mesa5 command sequence file/c file/s will bind file twice in Mesa 6, the first time copying onlycode and the second time only symbols. Compressed symbols are copied with the /x switch. In this mode, only the following symbols areincluded: all procedures, and the signals declared at the top level of modules. Symbols for theirparameters and results are not copied. This option allows limited but often adequate debugging,and substantially reduces the size of the symbols file (typically by more than 50%). To copycompressed symbols, SymbolCompressor.bcd must be loaded ahead of the Binder. Thus >Mesa.image SymbolCompressor.bcd Binder.bcd MySystem/xwill create MySystem.bcd and MySystem.symbols (compressed).Global switches are set by a command with an empty file name. In the form /switches, eachletter designates a different switch. The switches to copy code (/c), to copy symbols (/s), and tocompress symbols (/x) may now be given as global switches, and hence apply to all source filesthereafter. Unless a command to change the global switch settings comes first in the sequence ofcommands, it must be separated from the preceding command by an explicit semicolon. НЇОfЯtТНGОНЇОbНЇО^оpТ╣ТІxpПIНЇО](Т╒ПCxpxpНЇО[─Т НЇОX2П#Н╛ОUЇxН═p Н╛ОTxН═p Н╛ОRhxН═pН╛ОPаxН═pП5Н╛ОOxН═pxpxpН╛ОMrxН═pП9НЇОJ#xpП&НЇОFуТ² Т·ПYНЇОE-Т█П2Т▌П2НЇОC├ТП[НЇО@7Т╨xpxpПEНЇО>░ТП(НґО;AvТ─Н)`Н6 НґО8фxН)`Н6 pТНґО6KxН)`Т─Н6 pТН6 О4єpНґО2)xТ─Н)`Н6 pТоТпНЇО.зТ┼ xpПGТ▀НЇО-3Т┤xp xpvpТ┬НЇО+▄ТП'НЇО(=Т√Т≈xpП6НЇО&√Т╗ПXТ╘ НЇО$НТ╙ Т╚ПRНЇО#GТоПIТпНЇО!═ТИxpТЙП"ТНґОQxП6НЇОpxpxp НЇОЄТєПJТ╔xpНЇОТ≤Т≥П1xpxpНЇОeТґxpТўП.НЇОЎТ═П+Т║П6НЇОТПT `Їо=ГW<;Mesa 6.0 Binder Update5Associating File Names with Modules and ConfigurationsThe Binder now lets you control the association between file names and modules orsubconfigurations when you call it. This is done by specifying a list of component identifier-filename pairs inside brackets after the input file name. For example, the commandMySystem[Test: UnpackedTest]will bind MySystem.config using the previously bound configuration Test that is stored on thefile UnpackedTest.bcd. A command that includes one of these optional component-file namelists will have one of the forms: inputFile[id1: file1, ... idn: filen]/switchesoutputFile _ inputFile[id1: file1, ... idn: filen]/switches[key1: file1, ... keym: filem] _ inputFile[id1: file1, ...idn: filen]/switchesThe module or configuration named by idi in the configuration description will be read from thefile filei; .bcd is the default extension.Distribution: Mesa Users Mesa Group SD SupportЪНЇОfЯtТНGОНЇОbТXП6НЇО^оpТGПQНЇО](Т╛П#ТґП@НЇО[─ТПOНLОYxТвНЇОUЇpТ░Т▒xpП*zpНЇОTТіxpТїП8НЇОRhТП%НLОOМxОO`sОOМxТвОO`sОOМxОO`sОOМxОO`sОOМx НLОM∙ОMsОM∙xОMsОM∙xОMsОM∙xОMsОM∙x НLОK>ОJ╠sОK>xОJ╠sОK>xОJ╠sОK>wxОJ╠sОK>xОJ╠sОK>xОJ╠sОK>xН2юОIsОHФsОIsxОHФsОIsx НЇОFHpТ²П$Т·xОE╩sОFHpП7НЇОD}ТxОCПsОD}pxpНЇО?нНЇО>JТXНЇО<фНЇО;A╪Ї9v=Г.∙ыCopyright c Xerox Corporation 1980Inter-Office MemorandumToMesa UsersDateOctober 27, 1980FromJohn WickLocationPalo AltoSubjectMesa 6.0 System UpdateOrganizationSDD/SS/MesaXEROX Filed on: [Iris]Doc>System60.bravo (and .press)This memo outlines changes made in the Mesa system interfaces since the last release (Mesa 5.0,April 9, 1979). A number of internal changes made in the system and the microcode are alsodiscussed.This memo is intended as a quick guide to conversion, not a detailed specification of the changes.Names in square brackets refer to sections of the Mesa System Documentation or to other publiclyavailable reference documents (e.g., the Alto Operating System Reference Manual).External InterfacesMajor changes include integrated support for Alto extended memory and elimination of BasicMesa.The System also now exports versions of the following Development Software interfaces: Ascii,Format, Inline, Process, Runtime, Storage, String, System, and Time. (Note thatimplementation of these interfaces may not be complete.) Other changes are relatively minor.AllocDefsPrivate types and operations have been removed. AllocInfo, MakeDataSegment, andMakeSwappedIn are now defined in SegmentDefs, and temporarily duplicated here forcompatibility. [Segment Package]AltoDefsMaxVMPage has been increased to support up to a million words of memory; MaxMDSPageand PagesPerMDS have been added. [Segment Package]AltoDisplayMaxBitsPerLine has been changed to 608 (it was 606). Cursor, CursorBits, andCursorHandle define the location and format of the cursor. Coordinate, CursorXY, andMouseXY define the location and format of the cursor and mouse coordinates. [Display Package]AltoFileDefsSupport for the DiskShape and PartitionName properties of the directory's leader page hasbeen added. The definition of a file serial number (SN) has been changed to isolate the flag bits(directory, random, and nolog) into a separate structure (SNBits). [Alto Operating SystemReference Manual]ЪН!вОpТX qpН]ОgZrТiНІОbнsН]pТX Н-єsН7BpНІО]ьsН]pН-єsН7BpНІОX©sН]tН-єsН7Bp НЭОSиupНЇОM╧sТFП5НЇОGbpТ╙П+Т╚П4НЇОE╩Т©ПDТюНЇОD НЇО@еТ⌡ПYТ°НЇО?Т≈П-Т≤vpНЇО=vТП)vП&pНЇО9TtНЇО6pТ▌П,Т▐П3НЇО4^Т╧П'Т╨П0wpНЇО2ІwpТТwpwpwpwpwpwpwpТУ НЇО1ТоП]НЇО-юvНЇО+EpТ&П0Т'wpwpНЇО)·wpТУТЖw pП%НЇО'ВТtpНЇО$╗vНЇО"-wpТґП@w НЇО ├pТw ptpНЇО7v НЇО╪w pТ;Т<wpw pНЇОwpТнТоw pwpНЇОmwpТ≤Т≥П2tpНЇОvНЇОєpТюwpwpП.НЇОЭТ Т⌡П*wpП+НЇОUwpТтwpwpТуwpvНЇОўТpЪрЭр>ГcИ5Mesa 6.0 System Update2AltoHardwareThis new interface defines most structures of the Alto hardware, including the processor, display,keyboard, mouse, keyset, printer interface, disk, and Ethernet. [Alto Hardware Manual]AsciiThis new interface defines the ASCII control character codes; for compatibility, these continue to bedefined in IODefs. [StreamIO Package]BasicMesaThe facilities of BasicMesa have been replaced by procedures in the standard system and acommand line switch (/b) which can be used to destroy the display and keyboard packages (seeDisplayDefs and StreamDefs). MakeImage is no longer a standard part of Mesa.image,and must be loaded separately. [Section 3]BitBltDefsThe extended memory option now supports use of the normal and alternate bank registers, whosevalues are supplied in the unused word of the BBTable (this option is not supported under XMesa5.0 microcode (version 39)). AlignedBBTable (and BBTableSpace) can be used to properlyalign BITBLT argument records. [Alto Hardware Manual]CharIOThis new interface provides many of the functions of IODefs, but each operation takes aStreamDefs.StreamHandle as its first parameter, allowing formatted input and output to anystandard stream. [StreamIO Package]DirectoryDefsThis interface has been changed slightly to speed up directory searches (by about a factor of 3). Inaddition, support for subdirectories was added (see Alto Operating System Reference Manual). Thefollowing items have changed (note that a NIL DiskHandle does not imply the system directory):EnumerateEntries: PROCEDURE [ dir: DiskHandle, proc: PROCEDURE [CARDINAL, StreamScan.Handle, DEptr] RETURNS [BOOLEAN], inspectFree: POINTER TO READONLY BOOLEAN, lengthFilter: CARDINAL _ 0] RETURNS [index: CARDINAL];The procedure proc is called for each directory entry; free entries are passed only ifinspectFree^ is TRUE. If the lengthFilter is non-zero, only entries with a filename length equalto lengthFilter characters will be passed to proc.The following procedure inserts an entry into the directory; unlike Lookup, it does not create afile. If the file already exists, TRUE is returned (and fp^ is undisturbed).Insert: PROCEDURE [ dir: DiskHandle, fp: POINTER TO AltoFileDefs.FP, name: STRING] RETURNS [old: BOOLEAN];ParseFileName replaces ExpandFileName; it strips the leading directory information fromname, puts the result in filename (appending a period if necessary), and returns a stream (withaccess dirAccess) open on the directory in which the file should be looked up.ParseFileName: PROCEDURE [ name, filename: STRING, dirAccess: SegmentDefs.AccessOptions] RETURNS [StreamDefs.DiskHandle];НЇОfмtТНGООfЯНЇОbvНЇО_ёpТґПbНЇО]ШТПAvpНЇОZґvНЇОX2pТ▄xpП,Т█НЇОV┼Т wptpНЇОSНЇОOТўypП@Т╞НЇОMrw pТ╡w pТЁwpП!y pНЇОKкТtpНЇОH|v НЇОFpТ÷ПWТ═НЇОDZТ└П.wpvpТ┘НЇОB╡Т╛w pwpТґНЇОAТzpvpНЇО=╪vНЇО;ApТЗП5wp ТШНЇО9 wpТ╙П+Т╚НЇО7СТtpНЇО4єvНЇО2)pТ▀ПbТ▄НЇО0┌Т░П(Т▒vП&pНЇО.зТ÷П"Т═spw pvpНґО,_wТXzwНґО*╦НґО)zwzwzwzwНґО'izТFwНґО%бТXzwzwzwНЇО#GpТ. wpПAТ/НЇО!═wpТ┬sp wpТ┴П%НЇОЬТwpwpНЇО}Т╚Т╛П7wpНЇОжТП#spwpНґО[wТXzwНґОЄzТF wТXzwНґОzwzwНЇО▒pТш w pТэП.НЇОЙwpТ÷wpТ═П*НЇОCТwpП>НґО хwТXzwНґО zwП'НґО yzwЪ ^Ї 2=Г]ы}Mesa 6.0 System Update3The following procedures set and return the directory used for looking up files which do not specifya directory name (initially set to "░w pТw pwpТНЇО<ИwpНЇО:nТюТаwpwpНЇО8фwpТЫwpwpwpwpw pТЗНЇО7w pТП1ypНЇО4єТыП>wpТзНЇО2ЩТ╙ wpwpwpwpТ╚ НЇО1UwpТwpwpНЇО.зТзwpw pТшwpНЇО-3wpТw pwpwpНЇО*╦ПMНґО(=wТX zwНґО&√zwП,НґО$ zwНґО"sНґО лПCНЇОQpТ█П-Т▌wpНЇО╙ТП&tpНЇО[v НЇОЮwpТЛПEНЇО9ТsptpНЇОЎТ,w pzpТ-НЇОw pТ∙w pw pw pТ√НЇОoТ└Т┘wpwpНЇО хТ·П,Т÷wpw pНЇО wpТП$wptp fЇы>Г\2┴Mesa 6.0 System Update5StreamScanThis new interface allows overlapped disk input when reading from a stream. It is a transliterationof the same code from the Alto Operating System (version 17). The following are defined inStreamScan.mesa:Descriptor: TYPE = RECORD [ da: AltoFileDefs.vDA, pageNumber: CARDINAL, numChars: CARDINAL, -- private fields];Handle: TYPE = POINTER TO READONLY Descriptor;Init: PROCEDURE [ stream: StreamDefs.StreamHandle, bufTable: POINTER, nBufs: CARDINAL] RETURNS [Handle];GetBuffer: PUBLIC PROCEDURE [ssd: Handle] RETURNS [POINTER];Finish: PROCEDURE [ssd: Handle];Init sets up a scan stream from a disk stream. In addition to the stream, the client supplies a vectorof pointers to 256 word areas useable as disk buffers (bufTable). The number of buffers suppliedis nBufs. At least one buffer must be supplied (the normal stream buffer is also used). Each callto GetBuffer will return a pointer to the next sequential page of the file and returns the previousbuffer page to the buffer pool (first call returns data page 0; file page 1). The public fields of theHandle are correct for the page returned by the most recent call to GetBuffer. GetBufferreturns NIL when there are no more pages to be read. A call to Finish terminates the scan. Noother stream operations should be performed between Init and Finish. [Disk Streams Package]StringDefsCompareStrings lexically compares two strings and returns -1, 0, or 1 if the first is less than,equal to, or greater than the second; an optional parameter may be supplied to ignore casedifferences. All procedures in this interface now handle NIL string parameters. [String Package]SystemDefsCopyString allocates storage from the system heap and copies its argument into it, optionallymaking the new string longer. ExpandString performes a similar function, allocating a new string(and freeing the old one) if necessary. Even and Quad can be used to align pointers on doubleand quad word boundaries. [Storage Management]TimeDefsThe type HardwareTime has been replaced by InlineDefs.BcplLongNumber. Default valueshave been added to UnpackDT, PackDT, and AppendDayTime. ReadClock returns thecurrent value of the Alto's realtime clock (part of which can be found at locationRealTimeClock). [Time Package]TrapDefsStackError no longer takes a parameter; UnboundProcedure now takes an UNSPECIFIED. Thefollowing signals have been added (not all of which can be generated by Alto/Mesa):ZeroDivisor, DivideCheck, UnimplementedInst, WakeupError, PageFault, Write-ProtectFault, and HardwareError. [Traps]ЪНЇОfмtТНGООfЯНЇОbv НЇО_ёpТ▐ПCТ░П!НЇО]ШТгТхПFНЇО\TНґОYыwТXzwzwНґОX2НґОV┼ zwНґОTЦzwНґОS<{wНґОPаzwzТFwТXНґОNFzwНґОL·П-zwzwНґОJВzw НґОH| zТFwТXzwzwНґОFzwНЇОC├pТ│ПcНЇОAъТ┤ Т┬П,wpП"НЇО@7Т█wpТ▌П@НЇО>░Т▐wpТ░ПWНЇО<ИТ▓П2Т⌠П5НЇО;AwpТаП:ТбwpwНЇО9 pТ°zpП1Т²wpНЇО7СТ╦Т╧wpwptpНЇО4єv НЇО2)w pТ╠ПRНЇО0┌ТДП;ТЕНЇО.зТЎП9Т©spt pНЇО+▄v НЇО)w pТцТдПAНЇО'iТ├wpП)Т┤НЇО%бТ²П)wpТ·wpП(НЇО$ТtpНЇО лvНЇОQpТ┐wpТ└wpНЇО╙ТлwpwpТмwpwpНЇОТYП=ТZНЇО[wpТtpНЇОvНЇО▒w pТ┴Т┼wp z pНЇОЙТ5П:Т6НЇОCw pТRw pwpw pwpТSwНЇО⌡pТwptpЪ ЇT=ГYЇsMesa 6.0 System Update6XMesa Extended Memory SupportFunctions formerly provided by XMesa are now integrated with the standard system. A 3K RAM orMesa microcode in ROM1 is required to support the extended memory option. [Segment Package]Internal InterfacesThe following changes are internal to the implementation and do not affect public interfaces; theymay affect performance and/or space requirements, however. Note that Mesa 6.0 continues tosupport version 39 of the XMesa microcode available with Mesa 5.0; obviously, certain new featureslisted below are not available if your ROM contains the old microcode (e.g., Long BitBlt).3K RAM SupportMesa now supports the Alto 3K RAM option (available only on extended memory machines).Debugger BitmapIf the extended memory option is present, the system allocates part of the client's memory for useby the debugger for its display bitmap; this improves the debugger's response times considerably.The debugger bitmap may be deallocated by the procedure MiscOps.ReleaseDebuggerBitmapor the command line switch /k (in the former case, the call must be made before the debugger isfirst entered).Long Copy, Long BitBltThese opcodes now include support for extended memory.Misc OpcodesMisc opcodes (except for RCLK) now provide a general escape to user microcode in the RAM ifMesa is running on a 2K ROM or 3K RAM machine; they produce undefined results otherwise.Alpha bytes for the currently implemented MISC functions are defined in MiscAlpha.Overflow MicrocodeRunMesa has been upgraded to include microcode support for Pup checksums, IEEE floating point,and HBlt (used by Griffin). This microcode is loaded with the XMesa overflow microcode on Altoswith the 2K ROM (with version 41 microcode) or 3K RAM option. Users who have been loadingmicrocode for these functions need no longer do so. This change affects Alto IIs only.Range CheckingThe bounds check instruction (BNDCK) is now implemented correctly.Distribution:Mesa UsersMesa GroupSDSupportНЇОfмtТНGООfЯНЇОbvНЇО_ёpТ┌П$Т┐П4xpНЇО]ШТ╔xpТіП2tpНЇОYыtТНЇОV┼pТ⌡ПQТ°НЇОTЦТфПJТгНЇОS<Т└П8Т┘П*НЇОQ■ТП'xpП0НЇОNFv НЇОKкpТшxpТэНЇОH|vТНЇОFpТ≥П)Т П9НЇОDZТїПMТ╗НЇОB╡Т┌П-Т┐ wНЇОApТ≤ypТ≥П$НЇО?dТНЇО<vНЇО9 pП6НЇО6KvНЇО3пpТЇzpТ╦П7xpНЇО2)ТҐТЎxpxpП3НЇО0┌ТП*spwpНЇО-3vНЇО*╦pТ┘ПIТ├НЇО)Т┌Т┐ПXНЇО'iТєxpП#xpТ╔НЇО%бТПWНЇО"sv НЇОЬpzpНІО[Н хОЄ Н хО Н хОeЪйІо?ГW<ЫCopyright c Xerox Corporation 1979, 1980Inter-Office MemorandumToMesa UsersDateOctober 27, 1980FromJim Sandman, John WickLocationPalo AltoSubjectMesa 6.0 XMesa UpdateOrganizationSDD/SS/MesaXEROX Filed on: [Iris]Doc>XMesa60.bravo (and .press)This memo describes the changes in Mesa 6.0 runtime support which incorporate the facilities ofXMesa 5.0 into the standard system.Overview of Extended Memory SupportMesa now uses the extended memory of Alto II XMs as additional swapping space for code. Thismeans that code and data need not co-exist in the MDS, the primary 64K of memory. Mesa takesadvantage of any available extra space automatically; standard Alto programs do not need to bemodified to run. Support is provided for up to one million words of memory in blocks of 64Kwords. Because Mesa uses extended memory for code segments, it includes a page-level storage allocatorfor the additional banks. Client programs may request storage in the additional banks by usingextensions of the standard procedures in SegmentDefs. Mesa provides primitive mechanisms toread and write words in extended memory and to copy blocks of data between banks of memory,but gives no other assistance in accessing information in the extended memory. In particular,arbitrary use of LONG POINTERs is not supported on the Alto.Public InterfacesUnless otherwise stated, all of the facilities in this section are defined in SegmentDefs.Configuration InformationThe Mesa runtime system has an internal data structure that contains information about thehardware configuration of the machine on which it is running. Clients may obtain a copy of thisdata structure by calling GetMemoryConfig and should normally test for the existence ofextended memory by examining the useXM field. The extant banks of memory are indicated byMemoryConfig.banks, which is a bit mask (e.g., MemoryConfig.banks=140000B impliesthat banks zero and one exist). Note that this bit mask has been expanded to allow for up tosixteen banks; constants used to test against it must be changed.Н ОpТX qpН]Оg~rТiНІОcsН]pТX Н-єsН7BpНІО]ШsН]pН-єsН7BpНІОYsН]tН-єsН7Bp НЭОSЛupНЇОN#sТFП4НЇОG╗pТ╚Т╛П@НЇОFТП#НЇОAъtП#НЇО>░pТ⌠Т■ПPНЇО<ИТ▐ПQТ░НЇО;AТ╣ТІПNНЇО9 Т╚ПAТ╛НЇО7СТНЇО4єТ╘П%Т╙П:НЇО2ЩТЄПYТ╣НЇО1UТ≥П(Т v pП(НЇО/ўТ²Т·ПDНЇО.ТнПFТоНЇО,_ТwpxpНЇО(=tНЇО$НpПNv pНЇО лxТXНЇО}pТИТЙПRНЇОжТ÷П4Т═П,НЇО/ТСvpТТНЇО┤Т⌡Т°vpП4НЇОЮvtvpТ╡ ТЁxpvtvwvpНЇО9Т╦Т╧ПFНЇО▒ТxП1p Эр=Гd Mesa 6.0 XMesa Update2BankIndex: TYPE = [0..17B];ControlStoreType: TYPE = {Ram0, RamandRom, Ram3k, unknown};MachineType: TYPE = {unknown0, AltoI, AltoII, AltoIIXM, . . . };MemoryConfig: TYPE = MACHINE DEPENDENT RECORD [ reserved: [0..37B], AltoType: MachineType, xmMicroCode: BOOLEAN, useXM: BOOLEAN, mdsBank: BankIndex, controlStore: ControlStoreType, banks: [0..177777B], mesaMicrocodeVersion: [0..177777B]];memConfig: PUBILC READONLY MemoryConfig;GetMemoryConfig: PROCEDURE RETURNS [MemoryConfig] = INLINE BEGIN RETURN[memConfig] END;The field memConfig.useXM is true if and only if the following conditions hold:1)the machine is an Alto II with XM modifications (AltoType = AltoIIXM),2)the Alto has more than one memory bank installed (banks ~= 100000B),3)the Alto has a 3K RAM, or it has a second ROM containing an appropriate version ofthe XMesa microcode.The microcode version field tells only the microcode version, not the Mesa release number. (Forexample, for Mesa 6.0, mesaMicrocodeVersion is 41; Mesa 5.0 version 39 microcode is alsosupported, although not all features are available.)Extended Memory ManagementThe facilities described in this section can be used regardless of the state of useXM.Segments in extended memory are created with the usual primitives in SegmentDefs. However,additional "default" parameter values for those procedures that expect a VM base page numberhave been provided. DefaultMDSBase requests allocation anywhere in the MDS.DefaultXMBase requests allocation anywhere in the extended memory banks but not in theMDS. DefaultBase0, DefaultBase1, DefaultBase2 and DefaultBase3 request allocationin particular banks. DefaultANYBase requests allocation anywhere in the extended memorybanks or the MDS. DefaultBase is equivalent to DefaultANYBase if the segment is a codesegment, otherwise, it is equivalent to DefaultMDSBase.The following procedures convert between segment handles and long pointers, and work forsegments anywhere in the 20-bit address space.LongVMtoSegment: PROCEDURE [a: LONG POINTER] RETURNS [SegmentHandle];ЪНЇОfЯtТНGОН ОbvwТFvТXwvН О^оwТFvТXП%Н О[─ wТFvТXwvwvwvН ОX2wТFvТXwТFvТXН ОV┼Н ОTЦН ОS<wvН ОQ■wvН ОOМН ОNFП!Н ОL·Н ОJВП&Н ОG╗wТFvwН ОDZvwvТXwН ОB╡vwТFv wНЇО?dpТ vpП6Н О<НЮП1vpwpvpН О:nНЮП2vpwpvpН О8фНЮТ╒ТёПFНЮО7ТНЇО3пТїТ╗xp xpНЇО2)ТЇvpТ╦НЇО0┌ТП4НЇО,_xТXНЇО)pТПPvpНЇО%бТ∙ПAТ√v p НЇО$Т╪ПKТҐНЇО"sТ{v wpП(НЇО лvwТтpПAТуНЇО%ТґТўvpvpvpvpНЇО}Тнv wpТоП+НЇОжТ╠Т╡v pv pxНЇО/pТП!v pНЇОЮТМТНП@НЇО9ТП.Н ОЙvwvТXwvwvwТFvТXwvwЪ Їё>ГVhGMesa 6.0 XMesa Update3LongSegmentAddress: PROCEDURE [seg: SegmentHandle] RETURNS [LONG POINTER];LongVMtoDataSegment: PROCEDURE [a: LONG POINTER] RETURNS[DataSegmentHandle];LongDataSegmentAddress: PROCEDURE [seg: DataSegmentHandle]RETURNS [LONG POINTER];LongVMtoFileSegment: PROCEDURE [a: LONG POINTER] RETURNS[FileSegmentHandle];LongFileSegmentAddress: PROCEDURE [seg: FileSegmentHandle]RETURNS [LONG POINTER];The following definitions have been added to AltoDefs; they define parameters of the extendedmemory system.MaxVMPage: CARDINAL = 7777B;MaxMDSPage: CARDINAL = 377B;PagesPerMDS: CARDINAL = MaxMDSPage+1;The following procedures convert between page numbers and long pointers, and are analogous toAddressFromPage and PageFromAddress.LongAddressFromPage: PROCEDURE [page: AltoDefs.PageNumber]RETURNS [lp: LONG POINTER];PageFromLongAddress: PROCEDURE [lp: LONG POINTER]RETURNS [page: AltoDefs.PageNumber];The following procedures check the validity of long pointers and page numbers and raise theindicated errors.ValidateVMPage: PROCEDURE [page: UNSPECIFIED];InvalidVMPage: ERROR [page: UNSPECIFIED];ValidateLongPointer: PROCEDURE [a: LONG UNSPECIFIED];InvalidLongPointer: ERROR [lp: LONG UNSPECIFIED];The signal ImmovableSegmentInXM is raised when MakeImage (or CheckPoint) discovers asegment in the extended memory banks that cannot be swapped out. (See the section onrestrictions, below, for more information about image files).Long Pointer SupportThe facilities described in this section should be used only when useXM (see above) is TRUE.XCOPY is no longer implemented; clients should use InlineDefs.LongCOPY. It may only becalled when memConfig.xmMicrocode is TRUE.ЪНЇОfЯtТНGОН ОbvwvТXwvwvwvwТFvwН О^оvwvТXwvwvwТFvТXwНЮО](vwН ОYыvwvwvwvНЮОX2wvwТFvwН ОTЦvwvТXwvwvwТFvТXwНЮОS░ТЦП#ТДП8НЇО<ИТЇПГEъCopyright c Xerox Corporation 1980Inter-Office MemorandumToMesa UsersDateOctober 27, 1980FromBruce Malasky, John WickLocationPalo AltoSubjectMesa 6.0 Debugger UpdateOrganizationSDD/SS/MesaXEROX Filed on: [Iris]Doc>Debugger60.bravo (and .press)This memo outlines changes made in the Mesa Debugger since the last release (Mesa 5.0, April 9,1979); it is intended as a concise guide to conversion, not a detailed specification of the changes.Complete documentation on the Mesa 6.0 Debugger can be found in the Mesa DebuggerDocumentation.User InterfaceThe Debugger's user interface incorporates changes made in Tajo (the Tools Environment); thewindow package Wisk has been converted to use Vista, the new window package. For morecomplete documentation on the Tajo design, see the Tajo User's Guide and the Tajo FunctionalSpecification.TypeinThe assignment of some function keys and mouse buttons has changed. The menu button is nowYELLOW (formerly BLUE). FL4 is no longer the stuff key; use FR4 (Spare2), Keyset2, or ^S. Thefollowing function keys are implemented (see the section on editing for an explanation of thefunctions):FunctionADL KeyboardMicroswitch KeyboardKeysetControl KeyCutDELDELKeyset5^CPasteLFLFKeyset1^FNextFL3(none)Keyset3^NReplaceFL4(none)Keyset4^RSwatFR1Spare3(none)(none)StuffFR4Spare2Keyset2^SBack WordBWSpare1(none)^WReplace/NextFR5(none)(none)^KTypein is directed to the Debugger if the cursor is not in any window. Source windows will acceptinput until a file is loaded; they then direct typein to the Debugger (unless they are editable; seebelow).Н!вОpТX qpН]Оg~rТiНІОcsН]pТX Н-єsН7BpНІО]ШsН]pН-єsН7BpНІОYsН]tЫ(ЬЪЗЪН-єsЫЬЗН7Bp НЭОSЛupНЇОMЪsТFП7НЇОGbpТ≥П&Т П9НЇОE╩ТїП7Т╗П-НЇОDТ ТП.vНЇОBlpНЇО>JtТ НЇО:ШpТаП2ТбП*НЇО9TТ╪wpТҐwpП#НЇО7╛Т╧П"Т╨vpvНЇО6pНЇО2ІvНЇО/hpТ⌡ПWТ°НЇО-юspТҐ spspП!spspspТЎspНЇО,ТпП0ТяП-НЇО*r НґО&лЧ_О'#Н О&лЧ sО'#Т─Н'pО&лЧ ╗О'#Н7О&лЧО'#Н>`О&лЧ▌О'#НBНО&лЧuО'#ТНґО$╗xНІsН+─sН7─sНApНґО#xНІsН+─sН7─sНApНґО!YxНІsН+─pН7─sНApНґО╡xНІsН+─pН7─sНApНґОxНІsН+─sН7─pНAppНґОcxНІsН+─sН7─sНApНґО╪xТ─НІsН+─sН7─pНApsНґОxНІsН+─pН7─НApsНЇОфpТ┼П:Т▀П(НЇОТ║П<Т╒П(НЇОwЪ2Эр>Гd tMesa 6.0 Debugger Update2SelectionsThe selection scheme has changed. Clicking RED once selects a character, clicking twice selects aword, three times a line, etc. The selection can be extended to the left or right with BLUE; acharacter selection is extended by characters, a word selection by words, and so on. The currentselection is now video reversed.ScrollbarsScrollbars no longer occupy a dedicated part of the window, but instead come up on top of the leftedge. They are twice as wide as before, and you can "see through" them. To obtain a scroll bar,move left just past the edge of the window, then move right slightly, back into the window.Name StripeThe name stripe and tiny windows now video reverse when the cursor is in the sections thatfunction as accelerators for the window manager menu commands (Move, Grow, Size, Top,Bottom, and Zoom).MenusExcept for the change from BLUE to YELLOW, the way menus are invoked has not changed.However, some new menus and commands have been added.Standard MenusIn addition to Move, Grow, Size, Top, Bottom, and Zoom, the standard window manager menunow also includes the following command:DeactivateThis command deactivates the selected window; it will no longer appear on the screen andthe resources used by it will be freed. The window's name is added to a menu ofdeactivated windows, which is available outside all windows. The window may be madeactive again by selecting its menu item.A new Text Ops menu is now supplied with the Debug.log and source windows in addition to theWindow Manager menu. It contains Find, Position, Split, Normalize Insertion,Normalize Selection, and Wrap; the following commands are new:SplitThe Debugger's wisk window has been replaced by the more general Split windowcommand. Feedback is similar to that in Laurel: the split line can be picked up using REDand moved vertically. The subwindow is destroyed by moving the split line off the top orbottom of the (sub)window.Normalize InsertionFor windows containing an insert point (Debug.log and editable source windows), thiscommand will position the text in the (sub)window so that the line containing the insertpoint is at the top.ЪНЇОfЯtТНGОНЇОbv НЇО^оpТ╗П"Т╘ spП3НЇО](ТаТбП9spНЇО[─Т╗ПUТ╘НЇОYыТНЇОV┼v НЇОSГX+Mesa 6.0 Debugger Update3Normalize SelectionThis command positions the text in the (sub)window so that the line containing the leftmost position of the current selection is at the top.Debugger MenuA separate Debugger menu no longer exists; the Alter Bitmap function has been deleted, MoveBoundary has been superseded by Split (see above), and Stuff It is now available only on thekeyboard.Source MenusIn addition to the standard menus, the source window has two additional menus, Source Ops andFile Ops. The Source Ops menu contains the following commands, which are unchanged: Create,Destroy, SetBreak, SetTrace, and ClearBreak; the last three commands are available onlyif a file has been loaded into the window. The Source Ops menu contains the following newcommand:AttachCauses the Debugger to ignore the creation date of the current source file when settingbreakpoints or positioning to a source line. This command is essentially a LOOPHOLE;because the source-object correspondence may not be correct, it should be used with caution.If, after using Attach, the Debugger sets breakpoints in strange places, chances are thatthe source file does not match the version of the object in the system you are debugging.The File Ops menu includes the following new commands (plus Load, which functions as before):EditEnables editing of the currently loaded read only file (see below). Empty windows arealways editable, but because they have no backing store (until they are Saved or Storedon a file), the amount of information in the window should be kept small.SaveOutputs the contents of the window to its current file; overwriting the file requiresconfirmation. A backup "$" file is created that is a copy of the unedited version. After theSave command completes, access reverts to read only.StoreOutputs the contents of the window to the file named by the current selection; if the filealready exists, overwriting it requires confirmation. After the Store command completes,access reverts to read only.ResetDiscards all edits that have been made to the window (during this session) and resets accessto read only. If the file is not editable, the window is made empty.The Edit command is available only if a file has been associated with the window (by a previousLoad, Store, or Save); Store and Save apply only if the window has been edited.ЪНЇОfЯtТНGОНґОbxНґО_ёpТЇТ╦ПAНґО]ШТП5НЇОZґvНЇОW^pТ vpxpТ⌡ xНЇОUЇpТ─xpxpТ│НЇОTНЇОPаvТНЇОMrpТ║П&Т╒П)v pНЇОKкvТ┴pv pТ┼П appears in the Debug.log if you tryto Kill or Quit from the Debugger while editing a file.Caution: The editing facilities are designed not to alter the original file until it is Saved orStored, much like Bravo; the original contents are copied to a file with "$" appended to its name.This is however, a new facility and should be used with caution. It is designed to support amoderate number of localized changes to programs, not to replace your favorite document creationsystem.Debugger CommandsChanges in Debugger commands are relatively minor. The Debugger's interpreter is more generallyavailable and more consistent with the language. Tracepoints have been re-implemented as a minorextension of the standard breakpoint facilities.Old CommandsAscii/Octal ReadThe Ascii and Octal Read commands no longer automatically increment the default valueproduced by ESC.Break/Trace PointsBreak and trace points can no longer be set by typing a source line, and the Break Module andBreak Procedure commands and corresponding Trace and Clear commands have beendeleted; the menu commands must be used.The distinction between trace and breakpoints has been removed. An optional command string cannow be attached to each breakpoint which will be executed when the breakpoint is taken. Atracepoint then becomes a breakpoint with a standard default command string. LIst Breaks listsboth break and tracepoints (List Traces has been deleted). Clear All Entries/Xits clearsboth break and tracepoints.НЇОfЯtТНGОНЇОbvНЇО^оpТьП\НЇО](Т║П&Т╒П:НЇО[─Т╗П@Т╘П#НЇОYыТєspspТ╔П9Н╛ОUЇsН═pТ≤П#Т≥П#Н═ОTН╛ОQ╦sТ─Н═ypТэТщП!Н═ОPТ spН╛ОM╧sТ─Н═ypТП/spН╛ОKasТ─Н═ypТ┼Т▀Н═ОI╨ТН╛ОGbsТ─Н═ypТП3НЇОC@Т▒xpxpТ▓НЇОA≤ТxpxpП(НЇО=vtpТлТмПPxpНЇО;оxpТ├Т┤ПFНЇО:'ТиП@ТйНЇО8─Т■П5Т∙П+НЇО6ыНЇО2ІtТНЇО/hpТ┘ПQТ├НЇО-юТ┤ПaНЇО,ТП0НЇО(йvНЇО%|xНЇО#pТвxpx pП+ТьНЇО!YТspНЇОxНЇО░pТ⌡П.Т°xpНЇОХxТЖpТВxpxpНЇОAТП(НЇОфТ┬П@Т┴НЇОТиТйПHНЇОwТ▄П$Т█П)xpНЇОпТ▒xТ▓pxpНЇО)Т PЇБ>ГY)=Mesa 6.0 Debugger Update5Tracepoints automatically invoke the normal Display Stack command processor (withsubcommand p(arameters), v(ariables), or r(esults) as appropriate). The q(uit)subcommand (not b(reak)) exits to the Debugger's command level, where the normal Proceedcommand continues execution of the client.The method of specifying conditional break and tracepoints has changed; see the ATtachCondition command in the next section.When an exit break is set, the Debugger breaks on any return of the procedure by setting the actualbreakpoint on a common return instruction. The Debugger has no way of telling which return wastaken if there is more than one. When asked to display the source line when at an exit break, theDebugger now shows the declaration line of the procedure instead of the last return statement.Case On/OffThe Debugger no longer ignores case, and the case commands have been deleted; identifiers must betyped with their correct capitalization.Control DELTyping ^DEL will now abort the display of long arrays and strings, as well as most searches. Thiskey combination no longer has to be held down to be recognized.COremapThis command now prints more information about some data segments; the (system-assigned) typescurrently recognized are heap, system, frame, table, bitmap, stream buffer, and Pup buffer.Unrecognized types (assigned by the user) are displayed as data(t); an unknown type is displayedas data(?).Display Process [process]The subcommand space (SP) can now be used to invoke the interpreter.Display StackThe new subcommand "g" displays the global variables of the module containing the currentprocedure. A space (SP) invokes the interpreter. If the source window is loaded with thes(ource) subcommand, the window will remember the appropriate context for settingbreakpoints.Interpret CallThe Interpret Call command has been deleted; the Debugger's interpreter should be used.There are no longer any restrictions on when the interpreter may be called.ReSet Context [confirm]This command now requires two keystrokes, to avoid conflict with the ReMote debuggeecommand (not yet implemented on the Alto). STart [address] [Confirm]This command now requires confirmation.ЪНЇОfЯtТНGОНЇОbpТHП$ТIxpНЇО`vТҐ xpТЎxpxpxНЇО^оpТ·xpП(Т÷xНЇО](pТП*НЇОZґТПKТ xНЇОYpТНЇОV┼Т┌П<Т┐П'НЇОTЦТ▀Т▄ПPНЇОS<Т▓П^Т⌠НЇОQ■ТаП'ТбП7НЇОNFxТ НЇОKкpТ│П:Т┌vНЇОJ#ТП(НЇОFуx НЇОDZpТ·zpТ÷ПRНЇОB╡ТП?НЇО?dxНЇО<ИpТ▄Т█ПBНЇО;AТЪПCТНЇО9 Т│П;xpТ┌НЇО7СТxpНЇО4єxtxНЇО2)pzpП,НЇО.зxНЇО,_pТжТвxpПDНЇО*╦ТФzpП0ТГНЇО)xpТDТEП-НЇО'iНЇО$xТ НЇО!═pТюx pТаПEНЇОЬТПKНЇО╙xНЇО/pТЬП@ТЫxНЇО┤pТП,НЇО9xtx НЇОЎpП'іЇw>ГU■Mesa 6.0 Debugger Update6New CommandsAScii Display [address, count]Interprets address as POINTER TO PACKED ARRAY OF CHARACTER and displays count characters (eachcharacter separately, not as a string).ATtach Condition [number, condition]This command replaces old style conditional breaks; it changes a normal breakpoint into aconditional one. Arguments are a breakpoint number and a condition, which is evaluated in thecontext of the breakpoint. The breakpoint number is displayed when the break/tracepoint is set,and may also be obtained using the LIst Breaks command.ATtach Keystrokes [number, command]Arbitrary command strings can now be attached to break and tracepoints; they are executed by theDebugger when the breakpoint is taken. Arguments are a breakpoint number and a commandstring terminated with a CR. A CR can be embedded in the command string by quoting it with ^V.ATtach Loadstate [filename]Like ATtach Image, except that the initial rather than the current loadstate of the image file isused; this command is for wizards only.Break All Entries/Xits [module]This new command is the same as Trace All Entries/Xits, except that breakpoints are set.CLear Break [number]This command clears breakpoints by number. Typing CR in place of a number will clear thecurrent breakpoint, i.e., the one that transferred control into the Debugger.CLear Condition [number]This command changes a conditional breakpoint into a normal one. Typing CR in place of anumber behaves as in CLear Break.CLear Keystrokes [number]This command clears any command string associated with the breakpoint. Typing CR in place of anumber behaves as in CLear Break.LOgin [user, password]This command sets the default user name and password for the debugging session. The new username and password are not written into the client's core image or onto the disk.ReMote Debugee [host]This command is not implemented on the Alto.Trace StackThis command is used when the Debugger breaks and enters the debugger nub ("//" mode); itdumps the Debugger's call stack in octal to the log. Change requests reporting Debugger problemsthat result in an uncaught signal or other problem should be accompanied by a Debug.log whichincludes the output of this command.НЇОfЯtТНGОНЇОbvНЇО^оxtxtxНЇО\TpТ▌ tps Т▐p tpНЇОZґТП'НЇОW^xtxtxНЇОTЦpТЬП@ТЫНЇОS<Т╘Т╙ПCНЇОQ■ТїТ╗ПFНЇОOМТП#x pНЇОL·xtxtxНЇОJ#pТ░П\Т▒НЇОH|Т©ПBТюНЇОFуТ▀zpzpТ▄П6zpНЇОC├xТtxНЇОApТ╗xpТ╘ПCНЇО?dТП'НЇО<xtxНЇО9 pТ╚xpП"НЇО6KxТtxНЇО3пpТфТгП'zpП$НЇО2)ТПMНЇО.зxtxНЇО,_pТиПIzp НЇО*╦Тx pНЇО'ixtxНЇО$НpТ▌П6Т▐zp НЇО#GТx pНЇОЬxtxtxНЇО}pТ⌡Т°П@НЇОжТПPНЇО┤xtxНЇОpП,НЇОЎx НЇОCpТўПLxp НЇО⌡Т▀П(Т▄П9НЇОТТ█ Т▌ПCxpНЇОMТП$Ъ╪Ї=Г]*Mesa 6.0 Debugger Update7InterpreterThe interpreter provides support for all of the new language features introduced in Mesa 6. Allcommands requiring numeric input now invoke the interpreter automatically (e.g., Octal Read:@p, n: SIZE[r]).GrammarA summary of the revised grammar is attached. The constructs ABS, ERROR, LONG, LOOPHOLE, MAX,MIN, NIL, POINTER TO, PROC, PROCEDURE, SIGNAL, WORD, and open and half open intervals have beenadded to the interpreter's grammar; type REAL has been added for output only. Type expressionsfollowing % must be enclosed in parentheses. The interpreter syntax Expression? has replacedthe Interpret Expression command; it prints the value of the expression in several formatsincluding octal and decimal.Target TypingThe interpreter now does a much better job of target typing. As a result, arguments to procedurecalls and right hand sides of assignments are type checked. In addition, assignments to enumeratedtypes now work correctly.The interpreter also does a better job of determining signed/unsigned representation. For example,any octal number is assumed to be unsigned.Symbol Lookup Even if a module has compressed symbols, the debugger will first look for the filemodulename.bcd to see if it is the original compiler output for that module (by checking theversion stamp). If so, it will use those symbols. Thus, there is no need to Attach Symbols if theproper file is on the disk. It makes sense to use compressed symbols for large systems and to alsohave present the complete symbol files for the specific modules undergoing detailed debugging. Output ConventionsIn display stack mode, variables declared in nested blocks are now shown indented according totheir nesting level.A "?" in a variable display now uniformly means that the value is out of range; ". . ." indicatesthat there are additional fields present which cannot be displayed due to lack of symbol tableinformation.When the debugger refers to a program module, it usually gives the address of its global frame, e.g.,"G: nnnnnB". If the module has not been started, the debugger now prints a "~" after the B. If amodule has not been started, the user should not modify the global variables of that module, norshould they be displayed, as they are uninitialized.New Error MessagesThe warning Eval stack not empty! will be printed if the debugger is entered via either aninterrupt or a breakpoint with variables still on the evaluation stack; this indicates that the currentvalue of some variables may not be in main memory, where the interpreter normally looks.Exceptions to this are at entry and exit breaks; the debugger has enough information to decode theНЇОfЯtТНGОНЇОb НЇО^оpТ╛ПSТґНЇО](Т╛ПPТґx НЇО[─Т pНЇОX2vНЇОTЦpТ├П#Т┤spspspspspНЇОSНЇОЬНЇО╙Т│Т┌ПMНЇОxТ─pПOТ│xpНЇО[Т╙П&vpТ╚НЇОЄТП4НЇО▒tНЇОCpТ╛xpТґНЇО⌡Т≥П.Т П9НЇОТТХП<ТИНЇОMТ▄П(Т█П:Ъ vЇ>Г]<Mesa 6.0 Debugger Update8argument records that are on the stack in this case (if the appropriate symbol tables are available).Before the debugger permits any breakpoints to be set using the source window, the creation date inthe source file is checked against the corresponding date recorded by the compiler in the BCD. Themessage Can't use of instead of version created will result ifthe versions do not match (but see the Attach source menu command above).The message Resetting symbol table! is displayed when the interpreter's scratch symbol tableoverflows; the command is retried automatically. The Debugger's performance decreases somewhatuntil the symbol table is reinitialized.If a program is compiled with cross-jumping, the debugger will print the warning Cross jumped!before displaying the source.InstallationFontsThe Debugger now requires a strike font named MesaFont.strike or SysFont.strike; aversion of Gacha10 is available on MesaFont.strike. Additional strike fonts are storedon [Maxc]. (Strike fonts which include kerning are not supported.)SwitchesInstalling the debugger with the /b switch will video reverse the display (i.e., white characters on ablack background).Memory Bank ManagementWhen running on machines with more than 64K of memory, the client system supplies space to theDebugger for its bitmap (unless all but one bank has been disabled; see below); the client candisable this option by using the /k switch or by calling a system procedure before the Debugger isfirst invoked (see the Mesa 6.0 System Update).It is also possible for the Debugger to be installed with more than one bank of memory availablefor code swapping; this is done by reducing the amount of memory available to the client using theRunMesa bank switches or the Alto Executive MesaBanks.~ command (in Executive version 11 orlater).MesaBanks.~This command establishes the default memory allocation available to client programs.Arguments can be in two forms: a sixteen bit octal mask (followed by an optional /bswitch) indicating the available banks; a one in bit position n of the mask (counting fromthe left) indicates that bank n is available. Form two is a series of decimal bank numberseach followed by the /x switch; each bank mentioned is excluded from use by the client.Note that a request to exclude bank zero will be ignored. If no argument is present, thecommand will display the current value of the bank mask.The MesaBanks.~ command establishes the available memory for each .image or .bcdprogram invoked directly by the Alto Executive. The default may be overridden byexplicitly using RunMesa to invoke the program and optionally specifying bank switches onits command line, before the .image file name. The bank switches have the same formatas the arguments to MesaBanks.~ (except that the /b switch is required in the case of aЪНЇОfЯtТНGОНЇОbpТ≈П&Т≤П?НЇО^оТ─Т│ПPНЇО](Т┴ Т┼ПPspНЇО[─Т╒xТёpxpxpНЇОYыТП'xpНЇОV┼Т┘xТ├ pП9НЇОTЦТ▌П1Т▐П.НЇОS<ТП(НЇОOМТ▀ПQxНЇОNFpТНЇОJ#tНЇОFуvНЇОC├pТеП"Тфxpx pНЇОAъТ░ Т▒xpП%НЇО@7ТxpП:НЇО<ИvНЇО9 pТ▌П!xТ▐pПBНЇО7СТНЇО4єvНЇО1UpТ┤П'Т┬П7НЇО/ўТ╪П'ТҐП7НЇО.Т▐П!xpП/Т░НЇО,_ТvpНЇО)Т·ПOТ÷НЇО'iТ┤П/Т┬П3НЇО%бТ┌Т┐x pП$НЇО$НґО лx НґОQpТЛП$ТМП0НґО╙ТфТгП3xНґОpТ║vpvpТ╒НґО[Т≈vpТ≤НґОЄТ║xpvpТ╒НґОТёПYНґОeТП8НґОЙТ⌠x pП"Т■xpxНґОCpТБТЦП9НґО⌡Т┬П&Т┴П3НґОТТ▒xpП,Т▓НґОMТ≈x pxpТ≤ ЪLЇ=Г]PMesa 6.0 Debugger Update9bitmask). In the absense of any bank switches, RunMesa always assumes that all banks areavailable to the client.Using these facilities, it is possible to set up the defaults so that the Debugger has extra banks ofmemory at the expense of the client program. For example, on a three bank Alto, the followingcommands might be used to set the default and then install the Debugger:MesaBanks.~ 2/xRunMesa.run 1/x XDebug.imageUnder this arrangement, the client would use banks zero and one, and the Debugger would usebanks zero and two (because bank zero is swapped onto Swatee, it can be used by both).Actually, because the client (by default) is also allocating space for the Debugger's display bitmap,the client actually has only one-and-one-half banks, and the Debugger has two-and-one-half; thiscan be changed by running the client with the /k switch, resulting in two banks available to each.Note that the MesaBanks.~ command affects all Mesa programs invoked by the Alto Executive,including the Compiler and Binder. So the above example would run the Compiler in only twobanks, not three; this can be changed by saying RunMesa Compiler on the command line, which,because there are no bank switches specified, defaults to all banks available (not really necessary inthis case, since the Compiler runs almost as well in two banks as in three). On the next newsession, the Debugger is smart enough to notice that the Compiler (or whoever) has smashed what itthought was in bank two. (It is also smart enough not to use any memory that the client owns, sothat the 1/x switch on the command line above is actually unnecessary.)Since there are a lot of options here, some "standard" examples of client and Debuggerconfigurations might be helpful:Two Banks: Normally, do nothing; client and Debugger will each have one-and-one-halfbanks. For small clients and better Debugger performance, use RunMesa 1/xMesa.image Client.bcd, which will give the client one bank and the Debugger two.(If you were to use MesaBanks.~ 1/x in this case, the Compiler would also be restrictedto one bank).Three Banks: As in the three bank example above.Four Banks: Use MesaBanks.~ 3/x to give the client and the Debugger two-and-one-halfbanks each and the Compiler three; use MesaBanks.~ 2/x 3/x and Client/k toincrease the Debugger's allocation to three banks and restrict the client to two. Obviously,this can be adjusted based on the size of the client and the desired performance of theDebugger.Extended FeaturesNearly all of Alto/Tajo is now included in the Debugger (Librarian support and communicationsare not). Accordingly, there is little (if any) distinction between UserProcs and Tools, and Fetch(the FileTool plus communications) which runs in the Debugger is the same as the FileToolprovided by Alto/Tajo. A copy of section 10 of the Tajo User's Guide describing the FileTool isattached to this memo.Distribution:Mesa UsersMesa GroupSDSupportЪНЇОfЯtТНGОНґОbpТ┼Т▀П=НґО`vТНЇО](Т═ПEТ║НЇО[─ТєТ╔ПBНЇОYыТПHНґОW^xНґОUЇНЇОSГ[^PDebugger SummaryVersion 6.0ASciiRead [address, count]Display [address, count]ATtachImage [filename]Condition [number, condition]Keystrokes [number, command]Loadstate [filename]Symbols [globalframe, filename]BreakAllEntries [module/frame]Xits [module/frame]Entry [procedure]Xit [procedure]CLearAllBreaks [confirm]Entries [module/frame]Traces [confirm]Xits [module/frame]Break [number]Condition [number]EntryBreak [procedure]Trace [procedure]Keystrokes [number]XitBreak [procedure]Trace [procedure]COremap [confirm]CUrrent contextDisplayBreak [number]ConfigurationEval-stackFrame [address] (g,j,l,n,p,q,r,s,v)GlobalFrameTableModule [module]DisplayProcess [process] (l,n,p,q,r,s)Queue [identifier] (l,n,p,q,r,s)ReadyList (l,n,p,q,r,s)Stack (g,j,l,n,p,q,r,s,v)Find variable [identifier]Kill session [confirm]LIstBreaks [confirm]Configurations [confirm]Processes [confirm]LOgon [user, password]OctalClear break [globalframe, bytepc]Read [address, number]Set break [globalframe, bytepc]Write [address, value]Proceed [confirm]Quit [confirm]ReSet context [confirm]ReMote debuggee [host] [confirm]SEtConfiguration [config]Module context [module/frame]Octal context [address]Process context [process]Root configuration [config]STart [address] [confirm]TraceAllEntries [module/frame]Xits [module/frame]Entry [procedure]StackXit [procedure]Userscreen [confirm]Worryoff [confirm]on [confirm]^Debug [confirm]Н% ОaвpqТXpН'шО_9rqrН ┌ОX©sН▀ОVяrsqstuqtsН▀ОTЦrsqstsqtsН ┌ОRУrsН▀ОQrsqstsН▀ОOrsqstsqtsН▀ОM,rsqstsqtsН▀ОK>rsqstsН▀ОIPrsqst sqtsН ┌ОGbrsН▀ОEtrsН▀ОC├rsqstsН▀ОA≤rsqstsН▀О?╙rsqstsН▀О=╪rsqstsН ┌О;оrsН▀О9АrsН▀О7СrsqsН▀О6rsqstsН▀О4rsqsН▀О2)rsqstsН▀О0;rsqstsН▀О.MrsqstsН▀О,_rsН▀О*rrsqstsН▀О(└rsqstsН▀О&√rsqstsН▀О$╗rsН▀О"╨rsqstsН▀О лrsqstsН ┌ОчrsqsН ┌ОПrsqsН ┌ОrsН▀ОrsqstsН▀О'rsН▀О9rsН▀ОKrsqstsqsvsН▀О]rsН▀ОorsqstsН.qОXxrsН0zОV┼rsqstsqsv sН0zОT²rsqst sqsv sН0zОR╞rsqsv sН0zОPаrsqsvsН.qОNсrsqsqst sН.qОLЕrsqsqsН.qОJВrsН0zОI rsqsН0zОGrsqsН0zОE-rsqsН.qОC@rsqstsqtsН.qОARrsН0zО?drsqsqst sqtsН0zО=vrsqstsqtsН0zО;┬rsqsqst sqtsН0zО9 rsqstsqtsН.qО7╛rsqsН.qО5ЎrsqsН.qО3пrsrsqsqsН.qО1ЦrsrsqsqstqsН.qО/УrsН0zО.rsqstsН0zО,rsqsqstsН0zО*+rsqsqstsН0zО(=rsqsqstsН0zО&OrsqsqstsН.qО$arsqstsqsН.qО"srsН0zО ├rsН2zО≤rsqstsН2zО╙rsqstsН0zО╪rsqstsН0zОнrsН0zОЮrsqstsН.qОРrsqsН.qОrsН0zОqsН0zО)qsН.qО ;rsqsr ┌ТЛVDЄDebugger Interpreter GrammarVersion 6.0StatementList::= Statement | StatementList; | StatementList; StatementStatement::= LeftSide Interval | LeftSide _ Expression |MEMORY Interval | Expression | Expression ?LeftSide::= identifier | ( Expression ) | LeftSide Qualifier |identifier $ identifier | number $ identifier |MEMORY [ Expression ] | LOOPHOLE [ Expression ] |LOOPHOLE [ Expression , TypeExpression ]Qualifier::= ^ | . identifier | [ ExpressionList ]Interval::= [ Bounds ] | [ Bounds ) | ( Bounds ] | ( Bounds ) |[ Expression ! Expression ]Bounds::= Expression .. ExpressionExpression::= SumSum::= Product | Sum AddOp ProductAddOp::= + | Product::= Factor | Product MultOp FactorMultOp::= * | / | MODFactor::= Primary | PrimaryPrimary::= Literal | LeftSide | @ LeftSide | BuiltinCall |Primary % | Primary % ( TypeExpression )Literal::= number | character | stringBuiltinCall::= NIL | NIL [ TypeExpression ] | PrefixOp [ ExpressionList ] |TypeOp [ TypeExpression ]PrefixOp::= ABS | BASE | LENGTH | LONG | MAX | MINExpressionList::= empty | Expression | ExpressionList, ExpressionTypeOp::= SIZETypeExpression::= identifier | TypeIdentifier | TypeConstructorTypeIdentifier::= BOOLEAN | INTEGER | CARDINAL | WORD | REAL | CHARACTER |STRING | UNSPECIFIED | PROC | PROCEDURE | SIGNAL | ERROR |identifier identifier | identifier TypeIdentifier |identifier . identifier | identifier $ identifierTypeConstructor::= LONG TypeExpression | @ TypeExpression |POINTER TO TypeExpressionН ВОaвpТiН'шО_ёqТX Н ┌ОYLН&П;Н ┌ОVяН&ЫхЬЪЗЪЫЬЗЫxЬЪЗЪ ЫхНQОU*rqЫЬЗН ┌ОR╞Н&ЫxЬЪЗ─ЫЬЗЫхЬЪЗЪЫЬЗЫхЬЪЗЪНQОQЫЬЗП/НQОO`rЫхЬЪЗЪqrqНQОM╧rqН ┌ОK>ЫЬЗН&ЫхЬЪЗЪЫЬЗЫxЬЪЗ─ЫЬЗ ЫxЬЪЗ─ЫЬЗН ┌ОHцН&ЫхЬЪЗЪЫ═ЫЬЗП8НQОGН ┌ОD═Н&ЫхЬЪЗЪЫ═ЫЬЗН ┌ОB% Н&Н ┌О?╙Н&Н ┌О=/Н& Н ┌О:ЄН&П#Н ┌О89Н&rН ┌О5ЎqН&Н ┌О3CН&ЫхЬЪЗЪЫЬЗНQО1°П(Н ┌О/!Н&ЫxЬЪЗ─ЫЬЗ ЫxЬЪЗ─ЫЬЗН ┌О,і Н&ЫxЬЪЗЪЫЬЗrqrqП3НQО*ЪН ┌О(└Н&rqrqrqrqrqrН ┌О& q Н&П5Н ┌О#▌Н&rН ┌О!q Н&П2Н ┌О≤ Н&rqrqrqrqrqrqНQОПrqr qrqrqrqrqНQОIП3НQО╒П1Н ┌О'Н&rqП$НQОrТF qТXЪД ┌87╗NZWisk SummaryVersion 6.0WHAT WISK MOUSE BUTTONS DO:Scroll BarText AreaREDScroll UpSelectYELLOWThumbMenuBLUEScroll DownExtendNAME STRIPE/SMALL WINDOW COMMANDS:LeftMiddleRightREDTop/BottomZoomTop/BottomYELLOWGrow (corner)Grow (edge)Grow (corner)BLUEMoveSizeMoveSTANDARD WINDOW MENU COMMANDS:MoveSizeBottomGrowTopZoomDeactivate STANDARD TEXT OPS MENU COMMANDS:Find [selection]Normalize InsertionSplitPosition [selection]Normalize SelectionWrapSOURCE WINDOW SOURCE OPS MENU COMMANDS:CreateSet Break [selection]Clear Break [selection]DestroySet Trace [selection]AttachSOURCE WINDOW FILE OPS MENU COMMANDS:Load [selection]Store [selection]ResetEditSave Н&■ОaвpТiН'шО_\qТX Н ┌ОZ┼Н+ОW*Ч╡ОW│rН5ОW*Ч<ОW│Н(▀ОW*ЧйОW│Н+ґОW*ЧОW│Н ┌ОTyН+Н(▀Н ┌ОRрН+Н(▀Н ┌ОQ+Н+ Н(▀Н ┌ОLXqП"Н+ОHЫЧsОIPrН(▀ОHЫЧAОIPН8+ОHЫЧeОIPН ┌ОGН+ Н(▀Н8+ Н ┌ОEtН+Н(▀ Н8+Н ┌ОCмН+Н(▀Н8+Н ┌О>ЗqН ┌О;РrНxН╣Н#KН*КН0шН8+Н ┌О7qН ┌О4rs Н ▀rН5+Н ┌О2ps Н ▀rН5+Н ┌О-²qП'Н ┌О*∙rН ▀ s Н5+rs Н ┌О(НrН ▀ s Н5+rН ┌О$qП%Н ┌О!rs Н ▀rs Н5+rН ┌ОkН ▀Ъ ┬ ┌$5-DАT/BGMMGT/BZoomSize/\RYBBYRRYBНrОUьЧGДНsОUьЧGДН,sОUьЧGДН@tОUьЧGДНrО^uЧ<GНrОU▒ЧП@ЮЬ8──┬┬┬┬┬┬┬┬┬╒ @┬ ─┬┬┬┬┬┬""""'Пiк┴кsг,┬"к!гqp┤"""""""""#Х╒@─ ,─┬L╒┴╡┬─#,є"(┬┬┌"┬┬─""""""┬┬┬╒(≤@─┼(─┬HЎ│╒P─"(°"(┬`B"┬├┬┬┬┬┬┬┬┬┬╒(└@┼(┬H │═P>"(є"(┬┌"┬│┬┬┬┬┬┬""""(╒H (┬H"┴(═P"#(є"(┬┴"┬┬─""""""""""'0─>iхПHpг ─""х·!гrp┤""""""┬┬┬═─ ─┬┬┬┬┬┬┬┬┬═┬ ┬┬┬┬┬┬""" pю""""""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" ЪЪЪЪЧ""""""┬┬┬║юъЪщч┬┬┬┬┬┬┬┬┬╒ _ъЪщч┬┬┬┬┬┬"""""╠г?с▌]р"""""""""!х╒й(┬_мu²л""""""┬┬┬═(╒┼┬щ}щэ┬┬┬┬┬┬┬┬┬═(╒┌Ъщ}щэ┬┬┬┬┬┬""""(і┌(─Ъмu÷э"""""""""!г│гЩс▌]э""""""┬┬┬═ЩЪЪЩЧ┬┬┬┬┬┬┬┬┬═ЪЪЪЪЧ┬┬┬┬┬┬""" ЪЪЪЪЧ""""""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═ЪЪЪЪЪЪЪЪЪЪЪЪЧ┬┬┬┬┬┬""" """"""""" """"""┬┬┬ёю─Пqг┬┬┬┬┬┬┬┬┬╒ @─┬┼(─┬┬┬┬┬┬""""'П▀┴├°p( (""""""""""(╒@┬┼I╒▀ю╗K""""""┬┬┬╒/≤@┬ЯхЎ`╗▄─┬┬┬┬┬┬┬┬┬╒(@─┌H═юи─┬┬┬┬┬┬""""(╒H─┌I╒┬┼─"""""""""#г0┬│Ф°p>sГ""""""┬┬┬═─┬┬┬┬┬┬┬┬┬═─┬┬┬┬┬┬""" """"""""" """"""┬┬┬═ЪЪЪЪЪЪЪЪЪЪЪЪЧ┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬╒ "П ┌┬─┬┬┬┬┬┬┬┬┬╒ $┬ ╙╙╙╙┬─@┬┬┬┬┬┬""""'╟(bб┬─0r"┼ Яф╙(╒ ┌┼(°CЮ┬┬┬┬┬┬┬┬┬╒! ─(▓┼ ┌AR("┼(єB┬┬┬┬┬┬""""(╒─$▓┼ ┌H╒R(&▀)єJ """""""""!г──"zr │ГQх rф·1ю""""""┬┬┬═─ ┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬║юП┬0┬┬┬┬┬┬┬┬┬╒ ┬┬H┬┬┬┬┬┬"""",╠г<┴┤╘к┴кB """"""""""╡й(░ ┼H╒╙,і ┼,└Р """"""┬┬┬╒╒▀Х Яф╙(╒ SХ└A@┬┬┬┬┬┬┬┬┬╒╒┼┌AR("RA@┬┬┬┬┬┬""""(╒┼(▓┌H╒R(&"(A@"""""""""!г"┴г │ГQх !х@─""""""┬┬┬═ ─┬┬┬┬┬┬┬┬┬═─┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═Ъ┬┬┬┬┬┬""" │""""""""" │""""""┬┬┬═│┬┬┬┬┬┬┬┬┬©ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪ│┬┬┬┬┬┬""" │""""""""" │""""""┬┬┬═Ъ┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" @@""""""┬┬┬ёю@──@ ─ю─ p┬┬┬┬┬┬┬┬┬╒ ── ─@─ ─ ┬┬┬┬┬┬┬""""'<╠г"p─q┌│г< °╘оП─,┬─ qо┼оrг""""""""""(░хH╒┬─"┼B─H░ ╒З$""@─╡┬─ $▀$▀(┬""""""┬┬┬ёо░┬O■Ь─"│б<─F >╙$>Р@─╒P─ └<┼$┼&┬┬┬┬┬┬┬┬┬╒H─H──"┌B─A ╙$ @─╒P─ D┼$┼!┬┬┬┬┬┬""""(▓─H┬┬"┼B─H▓╒╙$╒"H(╡P $─▀$└┼(─""""""""""'─Gp─°qБЬG °╘цА0─г, ─>цrцr'""""""┬┬┬═─ ─ ─┬┬┬┬┬┬┬┬┬═! ┬┬┬┬┬┬""" ю""""""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬║юПю8н┬┬┬┬┬┬┬┬┬╒$┬@─ "┬┬┬┬┬┬""""╠бq┌┴бЯб°╘о'sгqб"""""""""!д"й""┼B┼""B"╒З$"(┬┴┬"┼"""""""┬┬┬═$"▀Б"│б<▀Б>CБ>╙$>Р/┬Ы┬"cБ┬┬┬┬┬┬┬┬┬═$"┌"┌B┼ B ╙$ (│"┬┬┬┬┬┬""""$╒┌ "┼B┼""J ╒╙$╒(┬┴(─""┼ """""""""!ц│б°qБЯб1б°╘цгpгбqб""""""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═Ъ┬┬┬┬┬┬""" │""""""""" │""""""┬┬┬═│┬┬┬┬┬┬┬┬┬©ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪ│┬┬┬┬┬┬""" │""""""""" │""""""┬┬┬═Ъ┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" Ьо< >Ыюг >└Юю qюpю>""""""""" (╒ B┌ (─`┌ " @ ""┼ ┬ """"""┬┬┬═!ї,╒',Рю┌((═└!ю rх°╟,Яй╛rю" "┼`┬°rгr/q┬┬┬┬┬┬┬┬┬═"h╡х╒╗╡C ЯюK " ▀(╒х╪х╡B/╡▀ &r╒╒▀(─┼$▀ю┬┬┬┬┬┬""" "(╒(╒╗╒B ─ ▄─ #ЮЗ%>┬░/╒CЙ╒З ┼╒ ≤З&┼$┴""""""""" "(═(╒h═B ─ ─ "┌ ─░("B ╒┌▀ @└┌┼$┴""""""┬┬┬═"h═(╒h═J ┌ ─ " "┼"─░(╡J*╡┼ "┼ ─ ╒┼─┼d─┴┬┬┬┬┬┬┬┬┬═Ыї о<' 2 >│ю>#ГЬ▐░`!юr─г,1й╛r>`°qфЬ°rqёq┬┬┬┬┬┬""" ─ """"""""" @ @""""""┬┬┬═ю ┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" П8ю"""""""""" ┬@ *"""""""┬┬┬═┴й°Яюqоqг"ю┬┬┬┬┬┬┬┬┬═┼/╒B $▀ю*(і# ┬┬┬┬┬┬""" СЙ╒CЮ└┴("" """"""""" ▓ ╒BD┴("" """"""┬┬┬═┼*╒J $─┴(і ┬┬┬┬┬┬┬┬┬═┴й°1юцq"г" ┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" #─ ЮЮ>""""""""" ─ ─ """"""┬┬┬═P▀,`┤!дqб┬┬┬┬┬┬┬┬┬═P▄╡░┬╒""┼""┬┬┬┬┬┬""" P┬╒p┬╒!│┼"""""""""" Ь┬╒░┬╒ B┼"""""""┬┬┬═┬▄╒░┬╒"$┼""┬┬┬┬┬┬┬┬┬═┬▀"x┤!хqб┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" @sгp─pбю""""""""" ═─ ""┼─┴─""┬"&2 """"""┬┬┬═,cбp─,q╒ ┼─┼─"sю"≤ *2 ┬┬┬┬┬┬┬┬┬═2▒"┬─2┼bsа─"┴╗, BP@┬┬┬┬┬┬""" "q"┬─"┌"┼" ▐"│"╗2 ┌P─""""""""" "▒"┬─"┌"┬$@─"│"х"Ы""""""┬┬┬═╒▒""┬─2┼`"┼(──"┴ "┬"┬┬┬┬┬┬┬┬┬═"xбp┌,q╒░qо─ШЮpюp°#О┬Ю┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" 8>─┬sГ#юpаqю""""""""" ┬─┬0"┬(─b""┬"#┼ """"""┬┬┬═qиqб╠ф┬0"H─╒"sю"≤ "c┼┬┬┬┬┬┬┬┬┬═┼*┼"й)┬P0A#ю"┴╗"╔ю┬┬┬┬┬┬""" ┼┼"┼┬P"┌"/"│"╗""╔# """"""""" ┼ ┼"┼┬Ь"└ "│"х"/─B """"""┬┬┬═┬┼)┼"й)─"┴" "┴ "┬"!┌ ┬┬┬┬┬┬┬┬┬═qх┬qб╠ф┬q─Ыюpюp°!аЫю┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" └Ю── ">qгp─pгp@""""""""" ─ ""┼(─┴─""┬"(─┬ю""""""┬┬┬═!бp─,q╒ "┼i─┼─"sю"≤ (─┬ю┬┬┬┬┬┬┬┬┬═"""┬─2┼br╙──"┴╗, а@┬┬┬┬┬┬""" #Б"┬─"┌"┼╙─ ▐"│"╗2 "!@""""""""" ""┬─"┌"▀,─@─"│"х"$CЮ""""""┬┬┬═"""┬─2┼` ┼(───"┴ "┬"(─@┬┬┬┬┬┬┬┬┬═!бp┌,q╒ЎqгШЮpюp°!о┬Ь@┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" а8ЮЮ│!а!юp>▐─qю""""""""" ─ ─ ┐b#b ""┬──┼ """"""┬┬┬═╛qp┤ h┐ ╒c╒"sю"≤ │ ┬┬┬┬┬┬┬┬┬═╡▀а┬┬╒ ╒≤┘"╔"ю"┴╗ │1ю┬┬┬┬┬┬""" "┴Ь┬╒ ═┬┘"╔#/"│"╗ ┌ """"""""" ┴─┬╒ ═┬▐─>#/─" "│"х┌ """"""┬┬┬═ ┴┬┬╒ ╒≤"!" "┴ "┬└┼ ┬┬┬┬┬┬┬┬┬═ qp┤ ▀h│└ЫаЫюpюp░#Дqю┬┬┬┬┬┬""" ── """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" Ь8#ю┤!юp>┤qю""""""""" ─ "1┬─b ""┬┬─┼ """"""┬┬┬═╙б!гг" (2┬╒"sю"≤ ┬─┼ ┬┬┬┬┬┬┬┬┬═$Ш"""(┬(і#юP▀"ю"┴╗ ┤ю┬┬┬┬┬┬""" °╙">"(┬("" P▄─#/"│"╗ ┬┬" """"""""" є╙" "(┬(" Ь┬─" "│"х┬─B """"""┬┬┬═є╚"""(┬(і ┬─" "┴ "┬┬─┌ ┬┬┬┬┬┬┬┬┬═╙б!г"г!юЎГЫюpюp░#ГЫю┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" Ь8!юsГ!юp>┤p─""""""""" ─ " ┬(─b ""┬┬─┴─""""""┬┬┬═╙б!гг" ─H─╒"sю"≤ ┬─ ─┬┬┬┬┬┬┬┬┬═Ш"""(┬(і @╟G"ю"┴╗ ┴┬╗─┬┬┬┬┬┬""" └╙">"(┬(" ─х┬─#/"│"╗ ├┬╗─""""""""" └╙" "(┬("!>┬┬─" "│"х──х─""""""┬┬┬═└╚"""(┬(і┴─" "┴ "┬┬─┬─┬┬┬┬┬┬┬┬┬═╙б!г"г#ЮqЫюpюp░#ГsЮ┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" Ў▀Ю┌!гqю─p<г!ю""""""""" ┬─@├b(─┼ ─"┬ (─b """"""┬┬┬═P┤Пh┼╒(┼ ┬─"≤ (═ ┬┬┬┬┬┬┬┬┬═P┬╒@╒≤┌!к@┬─╗< к ю┬┬┬┬┬┬""" ▐≤@═┬┌",─ ▐┬▐"╗" ,┬ """"""""" ┬@═┬┌>"(─A┬─"х(─ """"""┬┬┬═ ┬╒H╒≤"(─┌D≤─"┬"(─" ┬┬┬┬┬┬┬┬┬═ ┤0▀h▐─ЫгШЮ8h─p°!гЫю┬┬┬┬┬┬""" ── """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═@┬┬┬┬┬┬""" Ю─00N""""""""" ──H─H""""""┬┬┬═┤<`─@─Aбp┬┬┬┬┬┬┬┬┬═┬░░─"ППB"┬┬┬┬┬┬┬""" ┬░p─"@─@B>`""""""""" ┬░░─"@─@B """"""┬┬┬═┬▓░─"@─@B"┬┬┬┬┬┬┬┬┬┬═┤x─@@Bp┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬═┬┬┬┬┬┬""" """"""""" """"""┬┬┬═┬┬┬┬┬┬┬┬┬©ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЭ┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""#ЪъЪЪЪЪВЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪР""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬▀©ъЪЪЪВЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЬ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬▀©ЪВЧОВЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЬ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬"""""""""""""""""""""#©aЧЙaгqЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪР"""""""""""""""""""""""""""""""""""""#©шЇЧИЇЖИўЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪР""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬▀©эВЧКЇЖКЁЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЬ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬▀©ъwЧКЇЖКҐЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЬ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬"""""""""""""""""""""#©шІЧИІЖКўЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪР"""""""""""""""""""""""""""""""""""""#┐эyЪyВ╠ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪР""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬▀ЪЪЪЪШЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЬ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬▀ЪЪЪЪШЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЬ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬"""""""""""""""""""""#ЪЪЪЪШЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪР""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼ЪЪЪЮ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬"""""""""""""""""""""">ЪЪЮ─Ю""""""""""""""""""""""""""""""""""""""©ОЪЮ─ """"""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼┼гЇC▌ ▀к╟K,""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼▀(─7ouю┴╒хL╡""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""R/─зО`┴╒┬H╒!B""""""""""""""""""""""""""""""""""""""R(зО═>┴╒─Х╒!B""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼S(─зМuю"≥(╒─,╡!@┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼"г=С▌ "hх°─+, ┌┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬"""""""""""""""""""""""ЩЪЪЮ ┌"""""""""""""""""""""""""""""""""""""""МЪЪЮ ─""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼бСЪЪЮ ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼ЪЪЪЬ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""cЪЪЪЬ <─┬""""""""""""""""""""""""""""""""""""""]ЪЪОЬ @"─┬""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼_N9ц┬╚Яю"q├─KЁб┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼_5жОp╛└B "┼I─L╒и┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""_tО╗└CЮ<Ых─H╒┴""""""""""""""""""""""""""""""""""""""_}ЖОxHB$┌H─Х╒│""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼]}жМpHJ "┼I─,╒│ ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼c~8s┬H1ю"qФ─+─б┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""ЪЪЪЬ""""""""""""""""""""""""""""""""""""""ЪЪЪЬ""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼ЪЪЪЬ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┼┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬▀ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЬ┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""<==<<НВОYтpТН@ИНВОU НВОQуqТ┬П.Т┴П5НВОPQТНВОM&pНВОIШqТ÷П2Т═П,НВОHwТНВОEKpНВОB qТбП_НО>Т4НВОpТНВОХqТ°ПNТ²НВОdТ:ю =ГZНVЪНЪОdЪЭ;╗:wPю█H5dpНЪОdЯ"y┼юKґ ДTajo User's Guide53Host: the name of the host to be used for remote file operations. If a connection is already open,any editing of this field causes it to be closed; if a transfer is in progress, the connectionwill not be closed until it is complete.Directory: the default remote directory. If empty, the value in the User: field is used.Source: a list of files (separated by spaces or returns) to be operated on. If the first character of afile name is "@", then the file is taken to be an indirect file and its contents are used as alist of files. Indirect files may nest.Dest'n: file name for the destination of a transfer. If this field is left blank, the file name is thesame as the source.Pages= number of free pages left on the disk. This item is read only.User:, Password: the primary directory and the associated password. This field is initialized fromthe value of the user's last Alto Operating System login. Editing of this field is local to theFile Tool and does not affect the user's login in the Alto Operating System.Update only store or retrieve the file if the source is newer than the destination (comparingcreation dates). The default is false.Connect:, Password: the secondary directory and the associated password.Verify request confirmation for each file operation. The default is false.10.4 Command SubwindowFile Tool commands are available in the second form subwindow. Some of the commands areaccomplished by a background process. Those commands clear the Command subwindow so that asecond operation cannot be invoked while one is under way. The Copy! command operates onlyon the local disk. It does not take a list of files to operate upon. Close! closes a remote connection(if there is one).It is important to remember that the commands are postfix; e.g., fill in the Host: and Source: fieldsbefore invoking the Retrieve! command. The following commands are available:Retrieve! transfers the file specified in Source: from the remote file system to the local disk. Thefile name must conform to the file-naming conventions on the remote host. You maydesignate multiple files by the use of * expansion only to the extent that the remote serversupports it. If the local file is already in use, the transfer will not be made and the message ":can't be modified" will be displayed in both the message window and the log window. See warning in Section10.6Local-List! lists all files on the local disk corresponding to the name in Source:. This commandwill expand *s and #s.Remote-List! lists all files on the remote file system corresponding to the name in Source:. Thismust conform to the file naming conventions of the remote host. You may designatemultiple files by the use of * expansion only to the extent that the remote server supports it(currently Maxc and IFS do, but differently).Copy! makes a copy of a local file on the local disk. Only a single file may be copied and *s and#s are not allowed.ЪНО\∙pТН;РНОWбrqТ▄П!Т█П>НИОVТ°П)Т²П6НИОTsТП(НОQ$r qТЪП*ТrqНОMжrqТ└ Т┘ПWНИОL.Т░ПPТ▒ НИОJ┤ТП(НОG8rqТ≥Т ПNНИОE▒ТНОBBrqПAНО>ТrТ▀qТ▄ПGНИО=LТ┴П!Т┼П?НИО;╔ТsqП6НО8VrqТлП$ТмП4НИО6╞ТП'НО3`rqП6НО0rqПFНО,pНО(ГqТ╩П>Т╪НО'cТ┴ПTТ┼НО%ъТ║П@rqНО$[Т─Т│П(rqНО"вТНО┬Т│ПMrqТ┌rqНОАТrqП0НО▓rqТ┬П"rqТ┴П)sqНИОКТгПRНИОDТ▒Т▓ПDНИО°Т∙ tП1Т√П.НИОТ└П$Т┘ПGНИО■НОFr qТ≤П4Т≥rqНИО ·ТНО PrqТ┘ПIuqТ├НИО╗ТнПHТо НИОТ└ПRТ┘НИОZТП-НОrqТ┼Т▀П]НИОdТ╒Ї \=Г]╞:Tajo User's Guide54List-Options! creates a List Options window if one does not already exist.Store! transfers the file specified in Source: from the local disk to the remote Host. Alto filename conventions apply to the local file.Local-Delete! deletes the files specified in Source: from the local disk. If the local file is already in use,the delete will be skipped and the message ": can't be modified" will be displayed in both themessage window and the log window. See warning in Section 10.6Remote-Delete! deletes the file specified in Source: from the remote file system. You maydesignate multiple files by the use of * expansion only to the extent that the remote serversupports it.Close! closes the currently open FTP connection.If Verify is TRUE, then for each file that might be acted upon, the following commands aredisplayed Confirm! do the operation.Deny! abort the operation.Stop! abort the operation and terminate the command. This will close the connection with the server if aretrieve is being aborted.10.5 List Options windowThe List Options window is created by the List-Options! command. The properties that will bedisplayed, in addition to the file name, by a Local-List! or Remote-List! are governed by thebooleans in this window. After changing the options, use Apply! to effect those changes. TheAbort! command will restore the options which existed before the List-Options! command wasselected. Choosing either of the commands in the List Options window will cause that window tobe removed.If the Type attribute is requested for a Local-List! and the type is unknown, it will be listed as suchto prevent the time it would take to read the file and determine the type.10.6 ExceptionsThe actual transfer takes place in a background process, so the user is free to issue other commandsor even change the values in the parameter subwindow without affecting the command currentlyexecuting. Changing a parameter while the File Tool is waiting for Confirm! will not affect thename of the destination file; you should skip the transfer (by using Deny!) and reissue thecommand with the desired parameter correctly set.Warning: Do not attempt to use a file while it is being retrieved. This includes issuing commandsto the Debugger that cause it to try to reference the file. For example, Display Stack may causethe Debugger to reference symbols contained in the file being retrieved.Warning: If you are using the File Tool in the Debugger, be careful not to change any files outfrom under the program you are debugging; the file tool makes no provisions for checking if thefile is in use in the client world when you modify a local file.НОX√pТН;РНОSцrqП>НОPtrqТїП"rqТ╗П#usq НИОNмТП)НОK~rqТ┌Т┐rqtП$НИОIЗТ╡ТЁПYНИОHvТП?НОE'r qТйrqП"ТкНИОC─Т▒Т▓ПDНИОAыТНО>┼rqП+НО;_ТъrqvqП"ТЮП'НО9шТ НО6▄rqНО3=rqНО/ОrqТ▓П1Т⌠tП3НИО.GТНО*HpНО'qТґП*rqТўП&НО%≥ТиП.r qrqТйНО$Т╪П:rqТҐНО"▒rqТйП;rqТкНО! Т≥П_НО┴Т НО]Т─rqТ│r qП3НОыТПJНОзpНО╞qТ├Т┤ПQНО+Т╟П4Т╠П(НОїТ╞ПDrqpqТ╟НО"ТХТИП.rqНО ·ТП1НО PpТ▄ qП.Т█П+НО╗Т⌡П1Т°rq НОТПHНО╡pТ║ qТ╒ПPНОТёП_НОdТsqЪ |Ї[=ГY╟3Copyright c Xerox Corporation 1980Inter-Office MemorandumToMesa UsersDateOctober 27, 1980FromBruce MalaskyLocationPalo AltoSubjectDebugger: Extended FeaturesOrganizationSDD/SS/MesaXEROXFiled on: [Iris]Doc>XDF.bravo (and .press)DRAFTThis memo discusses Debugger User Procedures (UserProcs) and contains a sample Printer, a specialtype of UserProc.The Debugger is now the functional equivalent of the Alto/Tajo environment (with the exception ofLibrarian support and communications). As a result, there are no longer any differences betweenthe FileTool and ChatTool that run in Alto/Tajo and the versions that run in the Alto/MesaDebugger.Loading User ProceduresTo install the Debugger from the command line with some UserProcs, type:XDebug YourProc1[/l] YourProc2[/l] ... to the Alto Executive. To load files in an installed debugger, simply enter the Debugger nub; thendo a >New filename, followed by >Start globalframe. More information on the mechanism forloading programs into the Debugger can be found in the Mesa User's Handbook and the MesaDebugger Documentation.Hints for Writing User ProceduresThe Debugger gives you added help in gaining access to the information it already knows aboutyour program. The Debugger's configuration exports all of the Debugger's and Tajo's interfaces;see XDebug.config for details. A user program can access any of the Debugger's publicprocedures simply by importing the definitions modules of the procedures that you want to use.When writing your own debugging routines, look carefully at some of the utility routines that theDebugger already provides (e.g., Name, Frame, ShortREAD, etc.). In particular,DebugUsefulDefs contains most of the interesting procedures you might want. The interfaceDOutput contains utility procedures for displaying information in the Debug.log (a la IODefs).You should also look at the and directories for UserProcs that otherMesa users have already written and debugged.Warning: The Mesa Group makes no guarantees about the stability of these interfaces betweenreleases. Use at your own risk!Н!вОpТX qpН]Оg~rТiНІОcsН]pТX Н-єsН7BpНІО^sН]pН-єsН7BpНІОY)sН]pН-єsН7Bp НЭОSЛtНЇОMsТFП0Н? uНЇОFHpТ┬Т┴ vpП"vp НЇОD═ТНЇОARТ│Т┌ПUНЇО?╙Т╒ПAТёНЇО>ТЇwpwpТ╦П8НЇО<\НЇО9 xТНЇО5ЎpПHНґО3CyП'НЇО0хpТ▀П5Т▄П.НЇО/!Т╘ypxp ypx pxpП!Т╙НЇО-zТ╩Т╪П'vpvНЇО+рТpНЇО(└xП!НЇО%5pТўПWТ╞НЇО#▌Т╘П3Т╙П-НЇО!ФТХypТИПAНЇО ?ТЁП6ТЄП(НЇО≤Т═Т║ПUНЇОПТ│П!w pwpНЇОIwpТЇТ╦ПBНЇО╒wpТ⌠П?ypТ■wpНЇОЗТ∙Т√yzpypП%НЇОSТП-НЇОxТЮvТАП;НЇО]Т 2Эр>Гd Debugger: Extended Features2PrintersThe Debugger is capable of calling a user supplied procedure to print variables of specific types.To do this, a program must first register any type it will display by calling AddPrinter: PROC [type: STRING, proc: PROC [DebugOps.Foo]]from the interface Dump. The Debugger's interpreter evaluates type at the beginning of eachsession and remembers the target type of the result. Unfortunately, type is not a simple typeexpression, but rather a statement evaluated by the interpreter; the type is extracted from the result.Any additional information such as the address of a variable used when evaluating the statement is ignored.Later, whenever the Debugger encounters a variable of that type, it will call proc to display it. If,for a given printer, calling proc or evaluating type ever causes an UNWIND, the printer is nevercalled again. The parameter to proc is defined as follows:Foo: TYPE = POINTER TO Fob;Fob: TYPE = RECORD [ there: BOOLEAN, addr: BitAddress, words: CARDINAL, bits: [0..WordLength), . . .]];BitAddress: TYPE = RECORD [ base: LONG POINTER, offset: [0..WordLength], . . .];If there is TRUE, the BitAddress is a location in the user core image. For large structures,LongREAD and LongCopyREAD from DebugUsefulDefs should be used to access the data;for small structures the procedure GetValue in the interface DI (it takes a Foo as its argument)copies the information into the Debugger's core image and updates the addr. The Debugger ownsthe storage for Foos and the values copied into them from the user's core image; they are freed bythe Debugger between commands.A good technique for debugging the string used in the call to AddPrinter is to actually try it outusing the interpreter. All REALs could be intercepted by supplying the following STRING toAddPrinter:0%(REAL)The following STRING is used by the sample printer attached at the end of this memo.LOOPHOLE[1400B, StackFormat$Stack]^The constant 1400B is simply a location that is always mapped; AddPrinter's evaluation of the STRING does notactually use that location.Once StackPrinter is instantiated in the Debugger, PrintStack is called whenever the Debuggerwants to display a StackObject. Since PrintStack understands the format of StackObjects, itcan show the complete contents of a stack, something the Debugger is unable to do because of thezero length array.НЇОfЯxТНGОНЇОbНЇО^оpТ╙П2Т╚П0НЇО](ТПNНґОYыw{w{w{wНЇОV┼pТЇwpП'Т╦wpНЇОTЦТЎПEwpТ©НЇОS<Т├П/Т┤П8НЇОQ■|ТЯПUТРpНЇОNFТ▄Т█П2wpНЇОL·ТґТўwpwpspНЇОJВТwpНґОG╗w{w{ wНґОE-{w{wНґОC├pw{wНґОAъpwНґО@7pw{wНґО>░pwНґО<ИpwНґО:n{w{wНґО8фpw{wНґО7pwНґО5xpwНЇО2)pТюwp{pw pП1ТаНЇО0┌wpТ║wpwzpТ╒НЇО.зТёТєwpwpwpНЇО-3Т┼ПFwpТ▀ НЇО+▄Т┼wpП*Т▀П%НЇО)ДТНЇО&√Т▓П>w pТ⌠НЇО$НТЙТКspП2spНЇО#Gw pНґОЬwswНЇО╙pТ spП@НґО[{wТXyТвwНЇО0|ТІП6ТЇ{ |s|НЇО╛ТНЇО]pТ┤wxТ┬pxpw pНЇОІТ│w pw pТ┌w pНЇОТ│П#Т┌wpП7НЇОgТЪ \Ї >Г[КfDebugger: Extended Features3-- StackFormat.mesa-- Last Edited: Keith, October 21, 1980 10:30 PMStackFormat: DEFINITIONS = BEGIN Stack: TYPE = POINTER TO StackObject; StackObject: TYPE = RECORD [ top: CARDINAL _ 0, max: CARDINAL _ 0, overflowed: BOOLEAN _ FALSE, stack: ARRAY [0..0) OF CARDINAL]; END.-- StackPrinter.mesa-- Last Edited: Keith, October 21, 1980 10:38 PMDIRECTORY DebugOps USING [Foo, LongREAD], DI USING [GetValue], DOutput USING [Char, Line, Octal, Text], Dump USING [AddPrinter], StackFormat USING [StackEntry, StackObject];StackPrinter: PROGRAM IMPORTS DebugOps, DI, DOutput, Dump = BEGIN PrintRecord: PROC [lp, lps: LONG POINTER TO StackFormat.StackObject] ={ lpStack: LONG POINTER TO CARDINAL _ LOOPHOLE[@lps.stack]; IF lp.top = 0 THEN DOutput.Text["empty "L] ELSE FOR i: CARDINAL DECREASING IN [0..lp.top) DO DOutput.Octal[DebugOps.LongREAD[lpStack + i]]; DOutput.Char[' ]; ENDLOOP; IF lp.overflowed THEN DOutput.Text["(overflow!) "L]; IF lp.max = lp.top THEN DOutput.Text["(full!)"L]; DOutput.Line[" "L]}; PrintStack: PROC [f: DebugOps.Foo] = { g: LONG POINTER _ f.addr.base; DI.GetValue[f]; PrintRecord[f.addr.base, g]}; Dump.AddPrinter[ type: "LOOPHOLE[1400B, StackFormat$Stack]^", proc: PrintStack]; END.ЪНЇОfЯxТНGОНЇОbyТвНЇО` П2НЇО]▓НЇО\НЇОYП'НЇОUЩНЇОTyНЇОRУНЇОQqНЇОOМП%НЇОLЕНЇОHYНЇОFуП2НЇОCмНЇОBIП!НЇО@еНЇО?AП*НЇО=╪НЇО<8П.НЇО90П;НЇО7╛НЇО4єПHНЇО3 НЇО1°П=НЇО0П.НЇО.■НЇО-П2НЇО+▄ПHНЇО*НЇО(└П8НЇО'П5НЇО%|НЇО"sП(НЇО ОП"НЇОkП1НЇОcНЇОъПCНЇОв Ї=NQЪєCopyright c Xerox Corporation 1980Inter-Office MemorandumToMesa UsersDateOctober 27, 1980FromBrian Lewis, Jim Sandman, Dick SweetLocationPalo AltoSubjectMesa 6.0 Utilities UpdateOrganizationSDD/SS/MesaXEROX Filed on: [Iris]Doc>Utilities60.bravo (and .press)This memo outlines the changes made in the utility packages since the last release (Mesa 5.0, April9, 1979). More complete information can be found in the Mesa User's Handbook.Major changes include some new commands in the Lister and an extensively reworkedIncludeChecker. In addition, there is a version of the SignalLister that reads .bcd files.ListerThe lister is now available only as a .bcd file. The user interface has been changed slightly:commands that take string parameters no longer need string quotes. The command scanner takesall characters up to the next comma or right bracket as the parameter. ThusCode[ListerRoutines] and Code["ListerRoutines"]are equivalent. The new commands (and "improved" old ones) are listed below. Note that severalof the new commands (and some of the old ones) are useful only for internal (Compiler) debugging.CodeInConfig[config, module]OctalCodeInConfig[config, module]Config names a bound configuration; module is a module within that configuration. A codelisting is produced for the module (see the Code and OctalCode commands). This is ofparticular interest for packaged configurations where the code has been rearranged amongsegments and code packs.CompressUsing[file]The named file should contain a list of BCD file names. The using lists of the directorystatement are generated for each module in the list; they are then sorted to show for eachinterface, and for each item in the interface, which modules reference that item. The samecaveat about implicitly included symbols applies as for the Using command (see below).The output is written to file.ul.Hexify[], Octify[]The code lister normally prints addresses (and opcodes for "octal" listings) in base eight.For microcode debugging, base sixteen is sometimes preferable. Hexify[] puts the codelister into hexadecimal mode; Octify[] reverts to octal mode.ЪН!вОpТX qpН]Оg~rТiНІОcsН]pТX Н-єsН7BpНІО]ШsН]pП$Н-єsН7BpНІОYsН]tН-єsН7Bp НЭОSЛupНЇОN#sТП8НЇОG╗pТ░Т▒ПEНЇОFТП9vНЇОB╡pТ4П.Т5П#НЇОAТПPwpНЇО<ИtНЇО9 pТаТбwxpП4НЇО7СТ║П3Т╒П*НЇО6KТПLНґО2ЩwpТXwНЇО/ўpТ▀Т▄ПHНЇО.Т─П>Т│П#НЇО+EwtwТtwНЇО)·twtwНґО'#tpТ┌tpТ┐П*НґО%|Т∙П'Т√wpwpНґО#тТёПXНґО"-ТНЇОkw twНґОПpТґ ТўspП.НґОIТ≤П*Т≥П0НґО╒Т▌ПFТ▐НґОЗТ╘Т╙П0wpНґОSТwxНЇО▒wНґОpТ╞ПLТ╟НґОoТґП@wp ТўНґО хТwpЪ\Эр=Гd Mesa 6.0 Utilities Update2Implementors[file]The named file should contain a list of compiler output BCDs (interfaces and programmodules). This command creates a file, File.iml, showing for each interface exported byany program in the list, where the various interface items are implemented. If the list alsoincludes the BCD for a particular interface, the interface items not implemented by anyprogram are also shown. In order to run this command, one needs not only the BCDs in thelist, but also the BCDs for the interfaces exported by the programs therein. Missing BCDsare reported and the command attempts to forge on.Stamps[file]File names a compiler or binder output BCD. This command generates a file, File.bl,that shows the version stamps of any modules bound in the file, and of all imports andexports of the top level configuration in the file.UnboundExports[file]File names a compiler or binder output BCD. This command examines all of the exportedinterfaces and enumerates interface items in those interfaces that are not exported by thismodule or configuration.Using[file]Given a compiler output BCD, this command generates a directory statement with itsincluded identifier lists (on file.ul). Since there is not enough information in the BCD to tellwhich symbols were implicitly included, the USING clauses will contain a superset of those items actuallyneeded. The Mesa 6 Lister does a much better job of weeding out extraneous names in theUSING clauses.Version[file]File names a compiler or binder output BCD, or an IMAGE file. This command shows, onMesa.typescript, the object, source, and creator version stamps of the file.XrefByCallee[file], XrefByCaller[file]File names a file that contains a list of BCD file names. For each module in the list, a scanis made of the code to find all procedure calls. The pairs are then sorted byeither caller or callee. These commands produce output on file.xle and file.xlr,respectively.There are three kinds of procedure calls: local, external, and stack. The program can figureout which procedure is being called for local and external calls. Stack function calls areused for procedure variables (e.g., stream.get[...]) and for nested procedure calls. Theprogram ignores nested calls and indicates a callee of * for procedure variables.Include CheckerThe most significant differences between this version of the IncludeChecker and the one releasedwith Mesa 5.0 are the following:1.It handles more files, and requires less processing time for large numbers of files.2.It executes either from the command line or interactively.3.It obtains the creation dates for source files from their leader page, rather than fromthe first few lines of the source text (however, see the description of the new switch/t below).НЇОfЯtТНGОНЇОbwtwНґО_ёpТпТяspНґО]ШТ┘П(wpТ├П'НґО\TТ▒ПSТ▓ НґОZґТеspТфПAНґОYТ─ПMТ│spНґОW^ТіspП@spНґОUЇТП2НЇОRУwtwНґОPztpТ╚П#spТ╛wpНґОNсТ╡ПRТЁНґОM,ТП3НЇОJjwtwНґОGОtpТ√Т≈spП,НґОFHТіП)ТїП2НґОD═ТНЇОAъwtwНґО?dpТХsp ТИП)НґО=╪Т╟Т╠ wpyП/syНґО<8Т╨П,syП)Т╩НґО:ЄpТ▒П9Т▓НґО9 spТНЇО6KwtwНґО3пtpТ║Т╒spspНґО2)wpТП=НЇО/hwtwtwНґО,МtpТ▀П&spП1НґО+EТ└Т┘ПDНґО)·ТдП6ТеwpwpНґО'ВНґО%|Т┘П0Т├П-НґО#тТґТўПHНґО"-ТіП$zpП!ТїНґО ├ТП7wpНЇОctНЇОpТ╘П-Т╙П3НЇОmТНxОН┴ТїТ╗П:НxОпН┴ТЫхЬЪЗ─ ЫЬЗЫхЬЪЗ─П/НxО │ЫЬЗН┴Т└ПRТ┘Н┴ОзТ┼Т▀П<Н┴О 3wpТЪ НЇ Л=Г^tMesa 6.0 Utilities Update3There have been other minor changes to command syntax. The entire section of the Mesa User'sHandbook on the IncludeChecker is included below.The IncludeChecker is a program that examines a collection of Mesa source and BCDs forconsistency. It produces an output listing that gives a compilation order for the files, and for eachBCD, a list of all the BCDs that it includes, and a list of the BCDs which include it. Anyinconsistencies (which are described below) are flagged in this listing by an asterisk. As an option,the IncludeChecker will also generate a compilation command on Line.cm that can be executed tomake the files consistent. The IncludeChecker determines that an inconsistency exists among the input files if either: 1.A BCD includes another BCD with a version different from the one currently on the disk.This might happen, for example, if the included BCD had been recompiled.2.A source file is "newer" than the corresponding BCD. This could happen if the source hadbeen edited, or if the source had been retrieved from a remote file server. TheIncludeChecker compares the creation date of the source file against the creation daterecorded in the BCD of the source file from which the BCD was derived. The IncludeChecker operates in either command line or interactive mode. To use it in commandline mode, type to the Alto executive:>IncludeChecker [outputfile][/switches] [filename1 filename2 ...]whereoutputfile is the name of the file written. If no extension or switches are given, .listis assumed. If no file name is specified, the file Includes.list is assumed.filename1 filename2 . . . is the list of file names specifying the source and .bcdfiles to be checked. It is not necessary to give an extension, since the IncludeChecker willlook for any .mesa or .bcd file with the specified name. If no input files are specified,all .mesa and .bcd files on the disk are examined.To use the IncludeChecker interactively just type:>IncludeCheckerIt will then prompt for the output file name and switches, and then a list of the files to check.These are typed one at a time, and the list of file names is terminated by a CR. Typing ? CR ininteractive mode displays a short summary of the IncludeChecker's parameters and use.Each switch can be preceded by a - or ~ to turn it off. The switches are:/oPrint a compilation order in the output file (this is the default); -o suppresses thislisting./iPrint both the includes and included by relationships in the output file (default)./tObtain the creation date of source files from their leader page (default); -t willattempt to get the creation date from the first few lines of the source text. ЪНЇОfЯtТНGОНЇОbpТ·П.Т÷П$v НЇО`vpТП)НЇО](ТЗТШП/spНЇО[─Т⌠Т■ПVНЇОYыspТЙspП&spНЇОX2Т▓П[Т⌠ НЇОV┼Т├П?wpТ┤НЇОTЦТНЇОQ■ТЧПDТЪТНxОNFН┴Т╛ЫхЬЪЗ─sЫЬЗpЫхЬЪЗ─ТґsЫЬЗpЫхЬЪЗ─П=Н┴ОL·ТП0sЫЬЗpЫхЬЪЗ─НxОIPЫЬЗН┴Т▒П0spП"Т▓Н┴ОG╗Т ПPН┴ОFТыП0ТзП&Н┴ОDZТspП#sp НЇОAТ·Т÷П?НЇО?dТП&НґО<wТвПAНЇО8фpНґО5xw pТ├Т┤П7wНґО3пpТП4wpНґО0┌wТ╗Т╘pП5wНґО.зpТ∙П?Т√НґО-3Т wpТ⌡wpП@НґО+▄ТwpwpНЇО(=П2НґО$НwНЇО!═pТЁТЄПJНЇОЬТ║ПMwpТ╒ wpНЇОQТПUНЇОП!wpwpП#НґОЄwНЮpТ▌Т▐П=wpНЮОНґОЎwНЮpТ╘Т╙П8НґОowНЮpТўП?Т╞wpНЮО хТНП@ТОТЪ ▄Ї │>ГZ┼YMesa 6.0 Utilities Update4/cWrite a consistent compilation command in Line.cm (-c is the default). Inaddition, list as comments any BCDs and source files not on the disk which areneeded to do the compilation./mUse multiple output files (-m is default). The compilation order is written onsource.outputfile. The includes and included by relations are written ontooutputfile.includes and outputfile.includedBy, respectively. Thisswitch is useful if the output would otherwise be too large to fit into Bravo./nDo not compile source files that do not currently have corresponding .bcds on thedisk (-n is default)./pPlace a /p after every change of inclusion depth (see below) in the compilationcommand (-p is default). This will cause the Compiler to pause if errors arefound while compiling that or any previous module. /sSame as /c-i-o. This is used when only a consistent compilation command isneeded.The default switches are /oit-c-m-n-p-s.Note: The IncludeChecker only checks for consistency of the files that you specify. Thus, the list offiles that you give should include, for example, any important system files upon which your files aredependent. You should also inspect the compilation command before executing it, since the IncludeChecker'sidea of what should be recompiled may not be the same as yours. If a source file but no BCD is found on the disk, the IncludeChecker outputs a warning on thedisplay; in addition, it adds that file to the compilation command if /c and /-n are in effect. Awarning is also displayed if a BCD is found that was created by an obsolete version of the Compiler;its source file is also added to the compilation command. The IncludeChecker lists the file names of the compilation order and the consistent compilationcommand by inclusion depth, with the files that are the most deeply included first. Within thatconstraint, definitions modules are printed before program modules. In general, then, the "lowestlevel" definitions modules appear first, while the "highest level" program modules appear last. As an example of the IncludeChecker's use, the command line>IncludeChecker IC/c IODefs IOPkg LexiconDefs LexiconLexiconClientwill produce a consistent compilation command in Line.cm and the output shown below onIC.list.Compilation Order (by inclusion depth): LexiconDefs streamdefs stringdefs IODefs oldstringdefs systemdefs tty windowdefs IOPkg Lexicon LexiconClient IODefs (4-May-80 16:20:37 60#203#) (compilation source: 14-Apr-80 17:37:16)НЇОfЯtТНGОНґОbwНЮpТсТтП#wpwpНЮО`vТ╩spТ╪НЮО^оТНґО[─wНЮpТгwpТхП2НЮОYыwpТїП:НЮОX2wpТТТУwpНЮОV┼ТыТзП7НґОSНЇО)ДТґП*ТўП6НЇО(=Т═ПDТ║НЇО&√ТрП;ТсП$ТНЇО#GП;НґОЬwТвП5НґОQНЇОpТуТжwpНЇО[wpНЇОwТП'НЇОeП#НЇОЎНЇОП)НЇОoНЇО хНЇО yТ┼Т▀П; фЇ 2>Г]ыAMesa 6.0 Utilities Update5includes streamdefs stringdefsIOPkg (28-May-80 9:30:01 60#203#) (compilation source: 28-May-80 9:08:43) (source on disk: [same]) includes IODefs (4-May-80 16:20:37 60#203#) oldstringdefs streamdefs tty windowdefsLexicon (28-May-80 9:30:29 60#203#) (compilation source: 28-Apr-8017:02:20) (source on disk: [same]) includes IODefs (4-May-80 16:20:37 60#203#) LexiconDefs (14-May-80 10:48:49 60#205#) oldstringdefs systemdefsLexiconClient (28-May-80 10:02:50 60#203#) (compilation source: 28-May-8010:02:14) (source on disk: [same]) includes IODefs (4-May-80 16:20:37 60#203#) LexiconDefs (14-May-80 10:48:49 60#205#) oldstringdefsLexiconDefs (14-May-80 10:48:49 60#205#) (compilation source: 18-Apr-7919:19:11) (source on disk: [same]) includes nothingIODefs is included by IOPkg Lexicon LexiconClientIOPkg is included by nothingLexicon is included by nothingLexiconClient is included by nothingLexiconDefs is included by Lexicon LexiconClientBcdSignalsBcdSignals is an Alto/Mesa program which will produce a signal listing from a .bcd file; it worksmuch like the Alto/Mesa SignalLister for listing the signals in a .image file (see the Mesa User'sHandbook). To produce the signal listing Foo.signals from Foo.bcd, type to the AltoExecutive:ЪНЇОfЯtТНGОНЇОbwНЇО`vНЇО^оНЇО[─ТхП6ТиНЇОYыТП%НЇОX2П$НЇОV┼НЇОTЦНЇОS<НЇОQ■НЇОNFТюТаП(НЇОL·НЇОJВТП%НЇОIPП$НЇОG╗П*НЇОFНЇОDZНЇОAТеТфП1НЇО?dНЇО=╪ТП%НЇО<П$НЇО:nП*НЇО8фНЇО5xТ П(ТНЇО3пНЇО2)ТП-НЇО-3НЇО+▄НЇО)ДНЇО&√НЇО#GНЇОЬП$НЇО╙НЇОП%НЇОЮt НЇО╣pТ▒ПMТ▓wpНЇО1Т≤Т≥П+wpv НЇОґpТЯП!ТРw pwpНЇО) .ЇБ=ГY)оMesa 6.0 Utilities Update6>BcdSignals [octalNumber/switch] Foo[/switches]where/ntakes octalNumber to be the global frame index of the first frame inthis BCD. This will normally be the first free global frame index in thesystem into which the BCD will be loaded./xtakes octalNumber to be the StartPilot loadmap form of a global frameindex. This is the number in brackets beside the module name in theloadmap. It should be 200B times the octal number used with the /nswitch./plists the name, byte PC, and length of each procedure in Foo onFoo.procs./slist the signals of Foo on Foo.signals (default).As usual, a - or ~ can be used to invert the sense of the /s switch.Distribution:Mesa UsersMesa GroupSDSupportЪНЇОfЯtТНGОНґОbwП/НЇО^РpН═О\⌡wН═pТ╛w pТґН═О[ТєspТ╔П@Н═ОY⌠ТspН═ОW;wН═pТ┼w pП'Т▀Н═ОUЇТЁТЄП*Н═ОT3ТЁТЄП&xН═ОR╞pН═ОPWxН═pТЗТШП%wpН═ОNсwpН═ОL{xН═pТwpw p НЇОIPТXwpwpП(wpНІОB╡Н хОA Н хО?d Н хО=╪хІ=u8Ч*√░Copyright c Xerox Corporation 1980Inter-Office MemorandumToMesa UsersDateOctober 27, 1980FromJim Sandman, John WickLocationPalo AltoSubjectIntegrated Mesa EnvironmentOrganizationSDD/SS/MesaXEROX Filed on: [Iris]Doc>CommandCentral.bravo (and .press)This memo documents a small executive called Command Central; this Tool is intended to beinstalled with the Debugger and can be used to invoke the Compiler, the Binder, and clientprograms, all of which upon completion are directed to return to Command Central rather than tothe Alto Executive. The idea is that, while programming in Mesa, you enter Command Central'scontrol only once, and you rarely have to leave it; this is made possible by the editor that is nowincluded in the Debugger, as well as by the context switching facilities provided by CommandCentral.InstallationTo include Command Central in the Debugger, type the following Alto Executive command wheninstalling, after retrieving Fetch.bcd (which contains TinyPup, Stps, and the FileTool)and Utilities>CommandCentral.bcd. (If you have more than 64K of memory, be sure toconsult the Installation section of the Debugger documentation before proceeding.)>XDebug Fetch/l CommandCentral/lWhile it is possible to use Command Central without also installing the FileTool, including it willhelp minimize the number of times you have to leave the Mesa environment. If you have enoughmemory on your machine, you might consider installing other Tools with your Debugger as well(e.g., ChatTool, SendMessageTool).Note: Tools loaded via the command line are initially inactive (i.e., no window is showing); movethe cursor into the gray area outside all windows and use the menu found there to activate them.Entering Command CentralWhen using Command Central, the Debugger becomes the executive from which all programs areinvoked. To first enter this environment, type>Mesa/dto the Alto Executive. You can now use the FileTool to retrieve the modules you wish to work onand the Tools editor to modify them. When you have finished your changes, turn your attention tothe Command Central window.ЪНшОdpТX qpНaОbиrТiН ╨О^`sНapТX Н+╗sН5FpН ╨ОYFsНapН+╗sН5FpН ╨ОTPsНatН+╗sН5Fp НОO7upН ╩ОIJsТFП;Н ╩ОCpТгТхПPН ╩ОAoТшП+ТэП/Н ╩О?хТ∙ПPТ√Н ╩О>!ТёПEТєН ╩ОТ⌡Н ╩О06Т┬vpТ┴wpwp wpН ╩О.▌Т╠vП"pxП0Н ╩О,ГТПRН╠О)≤vН ╩О&JpТ⌠Т■П1wpН ╩О$╒Т▓П*Т⌠П3Н ╩О"ШТґПTТўН ╩О!TТwpwpН ╩ОТ²Т·ПOН ╩О^Т÷П1Т═П/Н ╩О_tТН ╩ОpТ°Т²ПHН ╩ОiТП/Н╠ОvН ╩ОкpТ┐Т└wpП,Н ╩О$Т┘П$Т├П=Н ╩О }ТЪLЭ╣=Гd*Integrated Mesa Environment2Command Central WindowThis window provides command lines for compiling, binding, and running your program, thecontext switching commands, and an option sheet; it also supports the standard window operations(scrolling, growing, etc.).<== ╞≤pb"┬╒╙┬B ╗░H┬┬╒(╙хB"╒╗╒░H┬"!г*╟B "їxb"" ─ b"┬═─H┬┬═─H┬" b"" b"┬═H┬┬═H┬" b""#│'Ю b"┬╒@"(─ H┬┬╒G,h r╙≤╠╗Ёк GH┬"#а2≤─ ▀Оєйh"иє H─b"""!"┬─ ┼╙°┼(>┴° ┬b"┬╒!"┬ ┼╙є┼( ┴$ ┬H┬┬╒!"≤"┼╙є┼h╒┴($!─H┬"#а"h─r╙·┴ї┬х!b"" ─b"┬═H┬┬═H┬" b"" b"┬═H┬┬═H┬" @b""#ю@ю ─b"┬╒ ░@ @"─H┬┬╒(╛┼" ┌*╒┬ "╙!┌╙H═│┬┬┬┬┬┬┬┬┼"к"┼*╡┬═╒╚!┼╙I╒┬┬┬┬┬"""""╡б qй╛┤ ╙аr╘Ф°"""""""""┌ ─"""""┬┬┬┼┌H ─┬┬┬┬┬┬┬┬┼┌0 ┬┬┬┬┬""""""""""""""""""┬┬┬┼┬┬┬┬┬┬┬┬┼┬┬┬┬┬""""@@"""""""""<Ю@┬@8─"""""┬┬┬┼"░┬$─┬┬┬┬┬┬┬┬┼"rх ▒кrюыгй≤iю$rф°╟h┬┬┬┬┬"""""▀(іПLі▀"з(єOє <)╒х╒≤""""""""""З(╒┬H╒З"шФJ°▀Ю"(Ў┬═┬"""""┬┬┬┼"┌(╒┬H╒┌╙$Jє┼"(═─═┬┬┬┬┬┬┬┬┬┼"▀)і┬Hі┼╙(єJє ")╒─╒≤┬┬┬┬┬""""┼( ▓(╒┌╙$Jє┼┬┬┬┬┬┬┬┬┼"й(┼h╒┼╙(єJє ┬┬┬┬┬"""""╠х ┴╗╒r╘г J·iю""""""""" """""┬┬┬┼┬┬┬┬┬┬┬┬┬┼p┬┬┬┬┬""""""""""""#ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪР"""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""<==<<НОU╠tТН<8НОPчНОM▐pТъПKТЮНОKХТ√ПNТ≈НОJ@ТНЖОFР,НО+bТАТБПJНО)╩Т┬vpТ┴xП'НО(ТПLНО$еpТ│vpvpvpТ┌П'НО#Т≤vpvpvpТ≥vpНО!vТ└vpvpvpvpТ┘НОоТ║ПLТ╒НО(ТЁТЄПPНО─ТПEНО2ТНП]НО┼vpТ·vpТ÷П)НОЦТ⌡ПZТ°НО<ТНОМТ vpТ⌡ПEНОFТ■П/Т∙П2НО ·ТҐТЎvpП)vpНОВТ≥П6Т vpНО PvpТНОТ▒Т▓ПHНОZТ┘Т├ПEНО╡Т▓Т⌠ПNНОТ┌Т┐ vpП/НОdТЪ■Ї@>ГVкЖЪНЪОdЪЭэ ■'╦█?н6ДpНЪОdЯ" 0LґWнюДIntegrated Mesa Environment3Invoking Other ProgramsAny Mesa .bcd which expects to be loaded into Mesa.image and obtains its commands from thecommand line (Com.cm) can be invoked by Command Central using the Run: field and the Run!command. (As above, the global /q switch is added to the command line so that control will return to the Debugger.)Some obvious programs which you might include on your disk are Access and Print.You can also run arbitrary .image and .run files using Command Central, but unless they havemade provision to return control to the Debugger, they will exit to the Alto Executive uponcompletion. Use the Mesa/d command to reenter Command Central.LimitationsIf you use the Compile!, Bind!, Run!, or Go! commands when you are in the middle of adebugging session (at a breakpoint or an uncaught signal, for example), the state of the client willbe lost. In particular, normal termination processing of the client will not take place (e.g., open fileswill be left dangling).Distribution:Mesa UsersMesa GroupSDSupportЪНО+ПtТН<9НО'НО#нpТ┬vpП!v pТ┴НО"'Т▄ vpТ█vpvНО pТ│ xПDТ┌П&НОьpТП?wpwpНО┴Т≤vpvpТ≥П2НОБТзПVТшНО;ТvpП$НОГ- ∙Copyright c Xerox Corporation 1980Inter-Office MemorandumToMesa UsersDateOctober 27, 1980FromHal Murray, Mark SapsfordLocationPalo AltoSubjectMesa 6.0 Pup and Ftp UpdateOrganizationSDD/SS/MesaXEROX Filed on: [Iris]Doc>PupFtp60.bravo (and .press)This memo outlines changes made in the Mesa Pup and Ftp Packages since the University releaseof December 20, 1979. This release is essentially a recompilation of the Pup and Ftp packagesusing Mesa 6.0. As usual, a number of bugs have also been fixed, and minor changes have beenmade to the interfaces. More complete information is available in the functional specificationsstored on Doc> as PupPackage.press and FtpPackage.press.Pup SummaryChangesThe following changes were made to Stream. The procedure types GetProcedure,PutProcedure, SetSSTProcedure, SendAttentionProcedure, and WaitAttention-Procedure now take a new initial argument sh: Handle. In addition, SendAttention-Procedure now takes a second argument byte: Byte (which is ignored), andWaitAttentionProcedure now returns a Byte (which should be ignored). As a result of thesetype redefinitions, the inline procedures SendAttention and WaitAttention have differentcalling sequences, and a new return value has been added to WaitAttention.The following changes were made to PupDefs. PupRouterSendThis no longer returns aSendReturnCode. SendReturnCode (a TYPE) has been deleted. If the buffer could not besent, it is discarded.The arguments to EnumeratePupAddresses are now named. The order of the two argumentsto PupAddressLookup has been reversed. The second argument to AppendPupAddress isnow a PupAddress, instead of a POINTER TO PupAddress. Similarly, the argument to Print-PupAddress is now a PupAddress, instead of a POINTER TO PupAddress. The local:PupSocketID argument to PupPktStreamCreate and PupByteStreamCreate has beenremoved.AdditionsThe procedures AppendHostName and AppendMyName have been added to PupDefs.UseAltoChecksumMicrocode has been added to speed up processing if you are running on anAlto with XMesa in the ROM or an Alto with a 3K RAM. The overflow microcode loaded into theRAM by RunMesa.run includes the necessary additions. (Beware if you load your ownmicrocode.)ЪН!вОpТX qpН]Оg~rТiНІОcsН]pТX Н-єsН7BpНІО]ШsН]pН-єsН7BpНІОYsН]tН-єsН7Bp НЭОSЛupНЇОMэsТFП5НЇОG?pТ⌡Т°ПCНЇОE≈Т╦П&Т╧П8НЇОCПТ÷ПAТ═НЇОBIТхПFТиНЇО@║Т v pvpvpНЇО<t НЇО90wНЇО5БpТEП"ТFxpxpНЇО4:xpТ═xpxpТ║x НЇО2⌠pТСП!xТТpx НЇО0ЛpТіТїx pНЇО/DxpТ xpТ⌡НЇО-²ТРП)ТСxpxpНЇО+ЖТПНЇО&√t НЇО#GpТїП0Т╗ xp НЇО!═ТеП&ТфП7НЇОЬТ xpНЇО╙П9НґО/НґО┤НґОЮНґО9П*x НґО▒pspxpНґОЙxpxНґОCpxНґО⌡pxp x НґОТpxpНґОMП5 ╡Ї=Г]Mesa 6.0 Pup and Ftp Update34499 FTPTransferFile doesn't pass through the creation date4544 FTPRetrieve hangs on a timeout on a "no" mark4763 Troubles if forget to call IdentifyNextRejectedRecipient5152 TimeExtras.PacketTimeFromString zone screwup5198 Config with server and user thingsDistribution:Mesa UsersMesa GroupSDSupportНЇОfЯtТНGОНґОbpxpП'НґО`vx pП"НґО^оxНґО](pxpНґО[─П'НІОTЦН хОS<ТX Н хОQ■ Н хОOМHІOі+≤e> TIMESROMAN MATH TIMESROMAN HELVETICA TIMESROMAN LOGOGACHA TIMESROMAN TIMESROMAN HELVETICA HELVETICA TIMESROMAN MATH TIMESROMAN HELVETICA TIMESROMAN LOGO TIMESROMAN TIMESROMAN HELVETICA GACHA TIMESROMAN TIMESROMAN TIMESROMAN TIMESROMAN TIMESROMAN HELVETICA HELVETICA MATH TIMESROMAN TIMESROMAN GACHA TIMESROMAN MATH TIMESROMAN HELVETICA TIMESROMAN LOGO TIMESROMAN HELVETICA GACHA TIMESROMAN HELVETICA TIMESROMAN MATH TIMESROMAN HELVETICA TIMESROMAN LOGO TIMESROMAN HELVETICA TIMESROMAN GACHA HELVETICA HELVETICA TIMESROMAN MATH TIMESROMAN HELVETICA TIMESROMAN LOGO HELVETICA HELVETICA TIMESROMAN TIMESROMAN TIMESROMAN MATH TIMESROMAN HELVETICA TIMESROMAN LOGO TIMESROMAN HELVETICA GACHA HELVETICA HELVETICA TIMESROMAN TIMESROMAN HELVETICA GACHA TIMESROMAN HELVETICA GACHA TIMESROMAN HELVETICA HELVETICA TIMESROMAN HELVETICA HELVETICA HELVETICA HELVETICA HELVETICA HELVETICA LOGO HELVETICA TEMPLATE@ TIMESROMAN TIMESROMAN HELVETICA TIMESROMAN TIMESROMANGACHA HELVETICAGACHA TIMESROMAN MATH TIMESROMAN HELVETICA LOGO HELVETICA TIMESROMAN HELVETICA TIMESROMAN GACHA HELVETICA HELVETICA TIMESROMAN TIMESROMAN MATH TIMESROMAN HELVETICA TIMESROMAN LOGO TIMESROMAN GACHA HELVETICA TIMESROMAN HELVETICA TIMESROMAN MATH TIMESROMAN HELVETICA TIMESROMAN LOGOGACHA HELVETICA TIMESROMAN TIMESROMAN MATH TIMESROMAN HELVETICA TIMESROMAN LOGOGACHA TIMESROMAN HELVETICA TIMESROMAN HELVETICA Э ▒фъ▄'э)Т0М6ж=ЄE ─NUq\═dДk÷skz р┐a▀b⌠ъ⌡Z╒ Ц╚═Ё /╪ўд5кхр█зъ8ДИ▐ЯеЬ'Шк┐ нw█$Щ+╧2∙8Ъ?▄EуLйSцZХaжhдp╟x╟─L├і▀▌9▐>ҐмфумщБД К\ОФЖ▄Чї© 1pЫ╪5k9╘@БGбI ЕB╔"*:ЎC:Z:Z" **▌J"9kФB"┐B":ДJФ: ;Z":ЕB:Z:Z⌡":·#:Ф:Е*:ЎC"┐B":ДJН":·#B":Е ":Е ":·#*if┌ !cic":ЕB"*:ЎC"*iW"ЩPЕ┼"iQ"*iM"ЩPЕ┼"iF"*iB": Е*╙P╙PіB"9hДJ " ┌ :Z "ЩPЕB!:Z%:Z&9XZ"* "9АФB" ┐B " :!ДJЛЩ]┌:Z#:Z$9dZ"*ia:]_C)┴▀ЖZЬВ")SЦ9╩НJ%O=O·Сґj/VMSЪЪ√&ZQЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪMesa60.presswick28-Oct-80 20:51:29 PSTS