Copyright c Xerox Corporation 1980Inter-Office MemorandumToMesa UsersDateSeptember 26, 1980FromDick SweetLocationPalo AltoSubjectMesa 6.0m Change SummaryOrganizationSDD/SS/MesaXEROX Filed on: [Igor]Doc>Summary60m.bravoThis memo outlines changes made in Mesa since the last alpha update (Mesa 6.0u, July 11, 1980).These changes will shortly be incorporated into the Mesa 6.0 Change Summary to correctly reflectthe differences between Mesa 5.0 and Mesa 6.0. This document also includes a list of ARs fixedsince 6.0u.LanguageThe language has been extended in the following areas:Monitor Locks and Condition Variables in RecordsWhen constructing a record, any fields not mentioned (and not having defaults) are not guaranteedto have known values after the construction. In particular, they are not guaranteed to have theirprevious values. This poses a problem in types containing "hidden" fields such as the queues ofprocesses in MONITORLOCKs and CONDITIONs, and with a few other types (see the attached memofrom Ed Satterthwaite). To protect users from inadvertantly overwriting these fields, the Mesa 6compiler does not allow updating of variables of these types, or of any composite type containing afield of these types. This does not mean that MONITORED RECORDs are read-only; they can beassigned to field by field. However, it is illegal to write a constructor for an entire MONITOREDRECORD except at the point of declaration (or allocation, by the NEW operator). SequencesA sequence is an indexable collection of objects, all of which have the same type. In this respect, asequence resembles an array; however, the length of a sequence is not specified at compile time.Consider some examples of "faked" sequences from Mesa 5.. . .ARec1: TYPE = RECORD [common: . . .count: CARDINAL, -- number of elementsbody: ARRAY [0..0) OF INTEGER];. . .ARec2: TYPE = RECORD [ЪН!вОpТX qpН]Оg~rТiНІОcsН]pТX Н-єsН7BpНІО]ШsН]p Н-єsН7BpНІОYsН]tН-єsН7Bp НЭОSЛupНЇОMЪsТFП/НЇОGлpТ П6Т⌡П)НЇОF$Т П8Т⌡П(НЇОD}Т╒ПMТёНЇОBжТ НЇО>вtНЇО;┬pП6НЇО89vП0НЇО4КpТ░ПRТ▒НЇО3CТіТїПHНЇО1°ТіТїПDНЇО/УТЁs pТЄspП4НЇО.MТґПNТўНЇО,іТ█ПGТ▌НЇО*ЪТаП$Тб spНЇО)WТІП>ТЇsНЇО'╟pТП;spНЇО$avНЇО!pТ▀vpП'Т▄П5НЇОkТ╙П3Т╚П-НЇОдТП8НґОIvНґО╒wswswpН(О'vwТXН(О╛vwspwpН(О1vwswpwsТF pНґО┴wТНґОБvwspswpbЭр>Гd Mesa 6.0m Change Summary2common: . . .body: ARRAY [0..0) OF INTEGER];ar1: POINTER TO ARec1;ar2: POINTER TO ARec2;The record ARec1 contains a count of the number of INTEGERs in body. The number of elements inan ARec2 is not contained in the record; it is kept elsewhere, say in a global variable, or computedfrom the values of common fields. Note that these "variable length" arrays occur only at the end ofrecords (they obviously couldn't occur in the middle). Also, since you aren't telling the compilerhow many elements are present in a given ARec*, it doesn't make sense to declare one; you obtainstorage from your favorite allocator and access the elements using a pointer.In Mesa 6, these constructs are built into the language. A SEQUENCE occurs as the last field of arecord. It optionally has a count of elements associated with the indexable portion. The followingMesa 6 declarations are roughly equivalent to the Mesa 5 ones above:. . .SRec1: TYPE = RECORD [common: . . .body: SEQUENCE count: CARDINAL OF INTEGER];. . .SRec2: TYPE = RECORD [common: . . .body: SEQUENCE COMPUTED CARDINAL OF INTEGER];sr1: POINTER TO SRec1;sr2: POINTER TO SRec2;Variables of type SRec* must also be dynamically allocated at runtime, since they are of variablelength. However, the NEW operator of Mesa 6 knows how to deal with sequences. Let z be anMDSZone, n a CARDINAL. The following are legal statements:(1)sr1 _ z.NEW [SRec1[n]];-- sets sr1.count to n(2)sr2 _ z.NEW[SRec2[n]];(3)sr1 _ z.NEW[SRec1[n] _ [common: . . ., body: NULL]];In statement (1), sufficient space is allocated to contain the common part of an SRec1 plus nelements (INTEGERs) in the sequence part. Additionally, the number of elements, count, is initializedto the value n. Thereafter, the value of count is readonly. The only way to set the length field of asequence is by the NEW operator. In statement (2), space is allocated for an SRec2 with n elements,but there is no count field to initialize. Of course, in any of these statements, n could be replacedby any constant or expression of type CARDINAL. In statement (3), the common fields are also set byan initializing constructor. Note that the "array" part of the sequence is voided in the constructor.In Mesa 6, there is no provision for writing a constructor for the variable length portion of aSEQUENCE. One must write explicit code to initialize it.ЪНЇОfЯtТНGОН(ОbvwТXН(О_ёvwswpwsТF pНґО\TvwТs wvpНґОYvws wvpНЇОUЇТ│ vpТ┌spvpНЇОTТ█vpП+Т▌П1НЇОRhТ─П<Т│П(НЇОPаТіПVТїНЇОOТ▌П)vpП2НЇОMrТПMНЇОJ#Т÷ Т═П2spНЇОH|Т░Т▒ПNНЇОFуТПDНґОDZwНґОB╡vwspspН(О@7vТXН(О=╪swvsТFpНґО<wТНґО:nvspspН(О7СvТXН(О5xsТFxТXsТFpНґО2)vТs wvpНґО.зvs wvpНЇО+▄ТіvpП@ТїНЇО)ДТ╚spТ╛П(vpНЇО(=vpТvpspП%Н2О$НН═vpТ─vswpvpvpН▐wТpvpvН2О!═pН═vpvspvpvpН2ОQН═vpvspvpvpvspНЇОТлПJТмvpvНЇО[pТ│ spП?Т┌vpНЇОЄТ⌠vpvp vТ■НЇОТ▐sv pТ░П.vpvp НЇОeТ⌠ПRТ■vpНЇОЎТ─П&spТ│П5НЇОТ⌠ПHТ■НЇОoТгП$ТхП;НЇО хspТП1 RЇ │>ГZ┼┘Mesa 6.0m Change Summary3To access an element of the sequence, one attaches an indexing expression to the pointer to therecord containing the sequence. This is analogous to the treatment of type STRING (which isessentially a sequence of the Mesa 6 variety).i _ sr1[j];sr2[j] _ i;If one compiles a module with bounds checking enabled (/b to the compiler), code will begenerated when accessing sr1[j] to assure that j IN [0..sr1.count).Alternative, on may write (analogous to saying s.text[i] for a STRING):i _ sr1.body[j];sr2.body[j] _ i;The attached memo from Ed Satterthwaite discusses the use and declaration of SEQUENCEs inconsiderable detail.FormatterThe Formatter is a program for transforming Mesa source files into a standard format. It uses theCompiler's scanner and parser to determine nesting, and hence can be used only on syntacticallycorrect programs. Attached is the Appendix from the Mesa 6 Users Handbook (in progress) thatexplains the use of the Formatter.BinderThe binder now allows the association between file names and module or configuration names to begiven on the command line, in much the same way as the compiler. For example, the commandline>Binder.bcd Tajo[TestPilot: UnpackagedTestPilot]will bind Tajo.config using the previously bound configuration TestPilot that is stored in thefile named UnpackagedTestPilot.bcd. One can best think of the the text inside the bracketsas defining (augmenting/replacing) a DIRECTORY statement at the beginning of the configuration.SystemAll of the system interfaces have been recompiled for 6.0m. This means that all modules must berecompiled/rebound to use the new Mesa.image. No source changes are necessary (except forusers of FTPDefs, as previously announced; see below).To track development in other systems, minor revisions have been made in the DevelopmentSoftware interfaces Format, Inline, Runtime, System, and Time.RunMesaRunMesa has been upgraded to included Alto microcode for Pup checksums, IEEE floating point,and HBlt (Griffin). This microcode is loaded with the XMesa overflow microcode on Altos withthe 2K ROM or 3K RAM option. Users who have been loading microcode for these functions needno longer do so. This change affects Alto IIs only.НЇОfЯtТНGОНЇОbpТ╠П_НЇО`vТжПLsp НЇО^оТП.НґО[─vpvpvpНґОYыvpvpvpНЇОV┼ТАП7ypТБНЇОTЦТvpvpvswpvpНЇОQ■П/vpvpspНґОNFvpvpvpНґОL·vpvpvpНЇОIPТтП=ТуzpНЇОG╗ТНЇОC╘tНЇО@[pТ⌠Т■ПRНЇО>ЁТґПIТўНЇО=ТєП+Т╔П2НЇО;eТП"НЇО7ftНЇО4pТ┐П-Т└П3НЇО2pТ║П/Т╒П+НЇО0хНґО-zyТП0НЇО*+pТ≥ y pТ wpНЇО(└Т■ ypТ∙П$НЇО&эТ╦П%spТ╧П$НЇО"щtНЇО▐pТ≈ПPТ≤НЇОГТ╞Т╟y pП.НЇО@ТwpП&НЇОЯТзП&ТшП2НЇОJТwpwpwpwpwpНЇОKtНЇОЭpТ°ПUТ²НЇОUТіТїПIНЇОўТ░Т▒{p{pПHНЇОТП4Ъ╦Ї ©=Г]L2Mesa 6.0m Change Summary4DebuggerIn addition to many bug fixes, the following changes and additions have been made:Source MenusAttachThe Attach menu command has been added to the Source Ops source menu; it causes theDebugger to ignore the creation date of the current source file when setting breakpoints orpositioning to a source line. Because this defeats type checking, this command should be used withcaution. If, after invoking this command, the Debugger sets breakpoints in strange places, chancesare that the source file does not match the object in the system you are debugging.CommandsReSet context [confirm]This command now requires two keystrokes, to avoid conflict with the ReMote debuggeecommand (not yet implemented on the Alto).Program-not-started IndicationWhen 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 tilde (~) after the B.If a module has not been started, the user should not believe and should not modify the globalvariables of that module.Command CentralThe options window has changed format and allows inclusion of default switch settings.Performance MonitorThe Performance Monitor has been upgraded to Mesa 6.0. It is the same as in Mesa 5.0 except thatdebugger breakpoint numbers are used for NodeIDs. Upgraded documentation will beforthcoming.Xfer CounterThe Xfer Counter has been upgraded to Mesa 6.0. A new mode of operation has been added togather information on the flow of control between groups of modules. Documentation for the XferCounter is attached.PupPupDefsUseAltoChecksumMicrocode has been added to speed up processing if you are running on anAlto II with the 2K ROM or 3K RAM option. The overflow microcode loaded into the RAM byRunMesa.run includes the necessary additions. (Beware if you load your own microcode.)ЪНЇОfЯtТНGОНЇОbНЇО^оpПRНЇО[─vНЇОX2yНЇОTЦpТыypП$v pТз НЇОS<ТЛП[НЇОQ■Т÷vТ═П+НЇОOМpТ√Т≈ПPНЇОNFТПSНЇОJВvНЇОG╗yНЇОDZpТЬП@ТЫyНЇОB╡pТП*НЇО?dvНЇО<pТ▄ПXТ█ НЇО:nyТ▀pТ▄ПTypНЇО8фТ╦Т╧П2vp НЇО7ТНЇО3 tНЇО/яpПVНЇО+рtНЇО(└pТ─Т│ПRНЇО&эТ:ПNТ;НЇО%5НЇО!6tТНЇОГpТ÷Т═ПJНЇО@Т┴П8Т┼П(НЇО≥ТНЇО tНЇОKvНЇОЭwpТ▄П?НЇОUТ╠{p{pП0Т╡{pНЇОўy pТМП@ТНdЇg>Г[єХMesa 6.0m Change Summary5Subtle implementation changesGetPupAddress will no longer return an address for a dying net. EnumeratePupAddresseswill now pass the client-supplied procedure addresses on dead or dying nets, but only afterprocessing all the addresses on nets that are reachable. (It used to skip addresses on unreachablenets.)The byte stream internals have been reworked to eliminate several unpleasant delays while openingand closing connections. It is now possible to open a connection, send a thousand words, and closethe connection in less than a second. (Since Close UnNews three module instances, it will takelonger if you have a lot of active global frames.) A byproduct of this cleanup is that SendNowwill send an empty aData packet to request an acknowledgment even if the previous SendBlockhappened to end on a convenient packet boundary.Bug fixesThe following change requests are closed by this release:5005 Delays when creating byte stream5093 NameLookup vs dying nets5098 Change priority of interrupt routine in EthernetDriver(s)FtpFTPDefsThe arguments to the (client supplied) procedure passed to FTPInventoryDumpFile have beenextended to allow proper processing of create dates. It is now compatable with the procedurepassed to FTPEnumerateFiles.Bug fixesThe following change requests are closed by this release:3987 StringBoundsFault from TimeExtras.PacketTimeFromString4444 FTPInventorryDumpFile needs create date4763 Troubles if forget to call IdentifyNextRejectedRecipient5152 TimeExtras.PacketTimeFromString zone screwup5198 Config with server and user thingsDistribution:Mesa UsersMesa GroupSDSupportЪНЇОfЯtТНGОНЇОbvНЇО^оwpТ▌Т▐П,wНЇО](pТКПFТЛНЇО[─Т║ Т╒ПUНЇОYыНЇОV┼Т░ПLТ▒НЇОTЦТ┬ПIТ┴НЇОS<Т╔ТіwpП,НЇОQ■Т÷Т═ПFwНЇОOМpТ░wpП0Т▒ wНЇОNFpТП0НЇОJВvНЇОG╗pП9НґОE-П%НґОC├w p НґОAъП-w pНЇО=ЮtНЇО:▒vНЇО7BpТїП0Т╗ wp НЇО5⌡ТеП&ТфП7НЇО3ТТ wpНЇО0╔vНЇО-VpП9НґО*шwpwНґО)4pwpНґО'█wНґО%ЕpwpНґО$>П'НІО║Н хОЫТX Н хОR Н хО╚ЪdІd=ГOїсInter-Office MemorandumToMesa UsersDateSeptember 25, 1980FromEd SatterthwaiteLocationPalo AltoSubjectMesa 6.0m Compiler ChangesOrganizationPARC/CSLXEROX Filed on: [Igor]Compiler60m.bravo (and .press)DRAFTThis memo documents additions and changes to the Mesa 6 language since the last alpha release(Mesa 6.0u, July 11, 1980). For a complete description of the differences between the Mesa 5 andMesa 6 languages, including the material below, see [Igor]Compiler60.bravo (or .press).SequencesA sequence in Mesa is an indexable collection of objects, all of which have the same type. In thisrespect, a sequence resembles an array; however, you need not specify the length of the sequencewhen its type is declared, only when an instance of that type is created. Mesa 6 provides sequence-containing types for applications in which the size of a dynamically created array cannot becomputed statically. Note, however, that only a subset of a more general design for sequences hasbeen implemented. The contexts in which sequence types may appear are somewhat restricted, asare the available operations on them. We believe that the subset provides enough functionality toaccomodate most uses of sequences, but you will encounter a number of annoying and sometimesinconvenient restrictions that you must take note of in your Mesa 6 programming.One can view a sequence type as a union of some number of array types, just as the variant part ofa variant record type can be viewed as a union of some (enumerated) collection of record types.Mesa adopts this view, particularly with respect to the declaration of sequence-containing types, withthe following consequences:A sequence type can be used only to declare a field of a record. At most one such field mayappear within a record, and it must occur last.A sequence-containing object has a tag field that specifies the length of that particular objectand thus the set of valid indices for its elements.To access the elements of a sequence, you use ordinary indexing operations; no discrimination isrequired. In this sense, all sequences are overlaid, but simple bounds checking is sufficient to validate each access.Uses of sequence-containing variables must follow a more restrictive discipline than is currentlyenforced for variant records. The (maximum) length of a sequence is fixed when the objectcontaining that sequence is created, and it cannot subsequently be changed. In addition, Mesa 6imposes the following restrictions on the uses of sequences:You cannot embed a sequence-containing record within another data structure. You mustallocate such records dynamically and reference them through pointers. (The NEW operationhas been extended to make allocation convenient.)Н]Оg║pТiНІОc8qН]rТX Н-єqН7BrНІО]ШqН]rН-єqН7BrНІОYqН]sН-єqН7BrНЭОSЛtrНЇОMqТFП9Н?┬vНЇОFHrТ╘П!Т╙П<НЇОD═Т⌠ПJТ■НЇОBЫТ┤ПbНЇО>вsНЇО;┬rТ√wrП#Т≈П6НЇО9АТ═ПPТ║НЇО89Т├Т┤ПJНЇО6▓ТФП.ТГП.НЇО4КТ■П.Т∙П4НЇО3CТ°Т²ПHНЇО1°Т П6Т⌡П,НЇО/УТ÷ПRТ═ НЇО.MТПPНЇО*ЪТ┬ПZТ┴НЇО)WТ╛ТґПVНЇО'╟Т│ПfНЇО& ТНLО#▌Т┴П+Т┼П1НLО!ФТП/НLОkТ√ПNТ≈НLОдТП3НЇОuТ╚Т╛ПEНЇОнuТёТєПPНЇОrТцП*ТдП7НЇОьТьТыП<НЇО1Т╘П^Т╙НЇО┴ТП<НLОТ╧ПAТ╨НLОgТ°П!Т²П,qr НLО юТП1Ъ фЭ y>Г^┴Mesa 6.0m Compiler Changes2You cannot derive a new type from a sequence-containing type by fixing the (maximum)length; i.e., there is no analog of a discriminated variant record type. There are no constructors for sequence-valued components of records, nor are suchcomponents initialized automatically.The following sections describe sequences in more detail.Defining Sequence TypesYou may use sequence types only to declare fields of records. A record may have at most one suchfield, and that field must be declared as the final component of the record:SyntaxVariantPart ::=. . . |PackingOption SEQUENCE SeqTag OF TypeSpecificationSeqTag ::=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]ЪНЇОfЯsТНGОНLОbrТбТцП=НLО`vТПIНLО]ШТ"ПLТ#НLО\TТП%НЇОYТXП9НЇОUЇwТНЇОRhrТ┐Т└ПBНЇОPаТПLНЇОMrwНLОJВx НеrТXН лxНеОIPrxН л qxqxНLОFуНеrН лx rxrx НеОE-rxН лqrx НLОB╡ НеrН лxНLО>░rН лxНеО<ИrxН л rx rНЇО9 ТЩxrx rТЧНЇО7Сx rТ┬xrТ┴П=НЇО6KТ┤ПJТ┬НЇО4єТ┐ПZТ└НЇО2ЩТ wrx rП$Т⌡НЇО1UТ НLО.зwrqrwrТXqrwrwrqrwrqrqrwrwrqrwrqrwrНЇО,_Т┌wrТ┐wrqrwrwrП+НЇО*╦ТНЇО'iТй ТкxrП9НЇО%бТ╦П5qrТ╧НЇО$ТНЇО лНLО}wrТXqrqrНLОжwrqrНLО/wrqrwrqrqrqТFwrНLОЮwrТXqrqrНLО9wrwrwrНLО▒w rqrwrqНLОЙrwrwrНLОCwrwrqТFrНLО⌡ТXwrwrqrwrqrqТFrНLОТТXqrРЇґ=Г[^┼Mesa 6.0m Compiler Changes3WordSeq: 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 (if given) must describe a zero-lengthsequence; i.e., it must account for just the space occupied by the tag field (if any). The CharSeqexample below shows how to deal with explicit positions and computed tags.Examples:Node: TYPE = MACHINE DEPENDENT RECORD [ info (0: 0..7): CHARACTER, sons (0: 8..15): SEQUENCE nSons (0: 8..15): [0..256) OF POINTER TO Node]CharSeq: TYPE = MACHINE DEPENDENT RECORD [ length (0): CARDINAL, char (1): PACKED SEQUENCE COMPUTED CARDINAL OF CHARACTER]Allocating SequencesIf S designates a record type with a final component that is a sequence, S[n] is a type specificationdescribing a record with a sequence part containing exactly n elements. The expression n must havea type conforming to CARDINAL. Its value need not be a compile-time constant; however, you canuse specifications of this form only to allocate sequence-containing objects (as arguments of NEW) orto inquire about the size of such objects (as arguments of SIZE). In particular, you cannot use S[n]to define or construct a new type or to declare a variable, even for constant n.The value of the expression SIZE[S[n]] has type CARDINAL and is the number of words required tostore an object of type S having n components in its sequence part.The value of the expression z.NEW[S[n]] has type POINTER TO S (or LONG POINTER TO S or REF S,depending upon the type of the zone z). The effect of its evaluation is to allocate SIZE[S[n]] wordsof storage from the zone z and to initialize that storage as follows:Any fields in the common part of the record receive their default values.The sequence tag field receives the value SUCCn[FIRST[T]], where T is the type of that field.The elements of the sequence part have undefined values.To supply initial values for the fields in the common part, you may use a constructor for type S inthe call of NEW. There are currently no constructors for sequence parts, however, and you mustvoid the corresponding field. In any case, you must explicitly program any required initialization ofthe elements of the sequence part. In Mesa 6, this is true even if the element type has non-NULLdefault value.НЇОfЯsТНGОНLОbwrТXqrqrqrqТFrТXqТFwrНLО^оuПhНЇО[─rТоwrП,wrТпНЇОYыqrТ▌wrwrwrxrТ▐П"НЇОX2ТП<НЇОTЦqw НЇОQ■rТ═Т║qrНЇОOМТ╒ТёПYНЇОNFТжТвПLНЇОL·Т°П1Т²П6НЇОJВТ÷Т═ПJwНЇОIPrТПJНЇОFНLОB╡wrТXqrqТFrТXНLОAwrqrНLО?dwrqrwrqТFrТXwrНLО<wrqrqТFrТXНLО:nwrqrНLО8фwrqТFrТXqТFrТXqТF rНЇО5xwТXНЇО2)rТ▒wrП&Т▓wrwrНЇО0┌Т─П3Т│wrwr НЇО.зТ⌡qrwrТ°П*НЇО-3Т├П'Т┤П7qrНЇО+▄Т░П)Т▒qrП"wrwrНЇО)ДТПNwrНЇО&√Т÷Т═qrwrwrqrП'НЇО$НТwrwrП!НЇО!═Т²wrqrwrwrq rwrqrwrТ·qrwrНЇОЬТ░П$wrП0qrwrwrНЇОQТwrП+НLОжТXПIНLО[П*qОХuО[rqrwr wrНLОЮП8НЇО▒Т▌П^Т▐wrНЇОЙТ╛qrТґПOНЇОCТ└П4Т┘П2НЇО⌡Т²ПOТ· qНЇОТrТ Ъ┌Їґ=Г[^ґMesa 6.0m Compiler Changes4Examples:ps: POINTER TO StackRep _ z.NEW[StackRep[100]];-- s.top = 1pn: POINTER TO Node _ z.NEW[Node[degree[c]] _ [info: c, sons: NULL]] pxn: POINTER TO extended Number _ z.NEW[extended Number[2*k]]Note that n specifies the maximum number of elements in the sequence part and must conform toCARDINAL no matter what BoundsType Ti appears in the SeqTag. The value assigned to the tagfield is SUCCn[FIRST[Ti]]. A bounds fault occurs if this is not a valid value of type Ti, i.e., if n >cardinality(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).Operations on SequencesYou can use a sequence-containing type S only as the argument of the type constructor POINTER TO(or REF). Note that the type of z.NEW[S[n]] is POINTER TO S (not POINTER TO S[n]). If the type ofan object is 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 thesequence's elements. A bounds fault occurs if the index is out of range, the sequence is notCOMPUTED, and you 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.ЪНЇОfЯsТНGОНЇОbrНLО_ёwrТXqТFrТXwrwrqrwrН.зwrwrНLО](wrqТF rТXwrqrwrwrwrwrwrqrНLОZґwrqТF rТXwrwrqrwrwrНЇОW^Т⌠ wrПRНЇОUЇqrТ·x rwОU*uОUЇrxrТ÷НЇОS┌Т°qОTuОS┌rqrwОRУuОS┌rП@wОRУuОS┌r wryНЇОQ╦w rwОQ+uОQ╦rТwrП$НЇОN▄Т┼qrwОMЪuОN▄rqОOuОN▄rqrwОMЪuОN▄r wrП;wОMЪuОN▄rТ▀НЇОLбТ√Т≈x rqrНЇОKТ÷ПTТ═НЇОIswrТ⌠П4wrx rТ■НЇОGлТ█Т▌wrwryrwr wrП/wrНЇОD}wТНЇОA.rТ┬П'wrП.qТ┴НЇО?┤rТ┘qrwrqrwrwrq Т├rwrq rwrwrНЇО=ЮТwrП-НLО;eТXП,НLО8ЙП)qrНLО6oНLО3ТПKqrНЇО0╔Т╞П/wrП&wrТ╟НЇО.ЧТБП2ТЦП*НЇО-VТП5НЇО*wrТ■Т∙ПLНЇО(`Т▄П)wrwrwrТ█П&wrНЇО&╧Тіx rПMНЇО%ТБТЦПKНЇО#jТмП8ТнП%НЇО!цqrТwrП$НЇОtТпП4ТяП(НЇОмТ≤П>Т≥П#НЇО&ТПBНЇОвНґО\wrwrwrwrТXwrwrwrwrwrwrwrНЇО wrТ├Т┤ q rП:НЇОfТ┬ПfНЇО©Т²qrП0Т·НЇО Т┌ q rТ┐ПCНЇОpТяq rТрП1BЇ)>Г\БЫMesa 6.0m Compiler Changes5You 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. This style willbecome mandatory in the safe subset of Cedar Mesa.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:STRING: 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 following types, which describe a structure similar to a StringBody as a true sequence, arepredeclared in Mesa 6. The type TEXT is primarily intended for users of Cedar, where the type REFTEXT (or REF READONLY TEXT) will replace most current uses of type STRING.TEXT: TYPE = MACHINE DEPENDENT RECORD [ length (0): [0..LAST[INTEGER]] _ 0, text (1): PACKED SEQUENCE maxLength (1): [0..LAST[INTEGER]] OF CHARACTER]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. This restriction is made so that"invisible" fields such as queues of waiting processes cannot be smashed in a variable that is alreadyin use.In Mesa 6, the following types have restricted assignment operations:НЇОfЯsТНGОНЇОbrТ┬П/q rqrНЇО`vТ┐П=Т└П'НЇО^оТНЇО[єuТ╚ПqНЇОZCТ│ПlТ┌НЇОXБТП2НЇОUЇrНґОS░ТXwrqТFrТXqrqrНЇО;AТ┬П<Т┴w rНЇО9 Т·П:Т÷П*НЇО7СТЇТ╦wrwrwrП*НЇО6KТтТуwrqrw rwrw rwrwrНЇО4єТ° qrwrqrwrwrТ²wrq rwrНЇО2ЩТ qП(rНLО0╔uТ║П?z uТ╒zuzuzuzuНLО/DТ▌q uzuzuП.Т▐zuzuq uzu НЇО,wТqНЇО(йrТаП7Тбw rНЇО'#Т┤П!qrТ┬qНЇО%|rТqrП)qrНLО#qrТXqrqТFrТXНLО!Ywr qrqrНLО╡wrqТFrТXwr qrqrqrqrНЇО░sТНЇОArТ┘П[Т├НЇО ТТПCНЇОРТ⌡ПdНЇОKТ▄Т█qrП-НЇОєТ┌ПMТ┐НЇОЭТНЇОўПE$Їg>Г[є╛Mesa 6.0m Compiler Changes6MONITORLOCKCONDITIONany 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 theentire variable cannot be updated; e.g., the timeout field of a CONDITION variable can be updated byordinary assignment. In Mesa 5, when a variable was allocated at runtime, it was necessary to call system procedures toinitialize any fields of types MONITORLOCK or CONDITION. If one uses the Mesa 6 NEW operator, thisinitialization takes place automatically as a result of the defaulting mechanism.Distribution:Mesa UsersMesa GroupЪНЇОfЯsТНGОНLОbq НLО_ёНLО](rТXqНLОZґrqНLОX2rТ╙qrТ╚П+НLОV┼ НLОTТ├qrП1Т┤ НLОRh НЇОOМТ┴Т┼ПZНЇОNFТіТїП?НЇОL·Т┬П-wrqrТ┴НЇОJВТНЇОH|Т≥ПbНЇОFуТ┬q rqrТ┴qrНЇОE-ТПQНІО>░Н хО<ИТX Н хО;A ЪўІ:З=Г-┘Formatter1Appendix B: FormatterThe Formatter transforms Mesa source files into a standard format. It establishes the horizontaland vertical spacing of the program in a way which reflects its logical structure.This appendix describes the formatting rules and the operation of the formatter, including the run-time options and messages.Preparing Source FilesSee this section in Appendix A: Compiler. Since the formatter uses the scanner and parser of thecompiler in order to determine structure, only syntactically correct programs may be formatted.ExamplesThe formatter takes commands only from the command line: follow "Formatter" with a list offilenames, separated by spaces. Let us consider first a few simple examples:The command>Formatter ProgNamewill read the file ProgName.mesa, copy its old contents to Formatter.scratch$, andassuming that it has no syntax errors, will produce a new, plain text, consistently formatted versionof ProgName.mesa.The command>Formatter ProgName/-tkwill read the file ProgName.mesa, and produce a two column landscape listing of the module inthe file ProgName.press. The program will be formatted using multiple fonts and faces.There are numerous other options described below.Command Line DescriptionThe simplest form of command is just the name of a source file to be formatted. If you supply thecommand sourcefile with no period and no extension, the formatter assumes you meansourcefile.mesa.During formatting, the display is turned off and the compiler's pass-one die is displayed in thecursor.The formatter reports the result of each command in Formatter.log with a message having oneof the following forms (each * is replaced by an appropriate number; bracketed items appear onlywhen relevant):ЪН'.ОfЯpНGОН"О\АqТiНЇОY⌠rТ╠ПFТ╡НЇОWКТПRНЇОT²Т⌠ПEТ■НЇОRУТНЇОN#pНЇОJтrТ≈ПZТ≤НЇОI-ТфП.ТгП1НЇОDZpНЇОArТ⌡Т°П/srНЇО?dТПMНЇО< НґО8фsНЇО5xrТ srТsrНЇО3пТ⌠ПeНЇО2)ТsrНЇО.з НґО+▄sНЇО(=rТ≤Т≥srП=НЇО&√ТКs rП/ТЛНЇО#GТП1НЇОtpНЇО&rТ┤П-Т┬П5НЇО~ТЖs rТВП-НЇОвsrНЇО┬ТҐП4ТЎП,НЇОАНЇО▓Т░П4srТ▒НЇО КТ≤ПTТ≥НЇОDТЪпЇЩ=Г\жFormatter2file.mesa -- source tokens: *, time: *Formatting was successful. The source file has been rewritten. The original can be foundin Formatter.scratch$. If several files are formatted in the same run, the original ofonly the last file will be in Formatter.scratch$.file.mesa -- aborted, * errors [and * warnings] on file.errlogFormatting was unsuccessful. The output of the formatter is undefined if syntax errors existin the input file. The original file is undisturbed.File errorThe formatter could not find the specified file.If any error or warning messages were issued, it brings this to your attention by putting "Type Key"into the cursor. The formatter will not return to the executive or run another subsystem until youacknowledge the message. (You can change this behavior by using switches, described below.)Formatting rulesGeneral RuleAs a general rule, the Formatter changes only the white space in the program. It does not insert ordelete any printing characters. On the other hand, it may insert white space where there previouslywas none. SpacingIndentation is done by a combination of tabs and spaces in plain-text mode (assuming that a tabequals eight spaces), and by spaces alone in Bravo formatted mode.The decision of where to break lines is made independently of the output mode: press file, plaintext, or Bravo looks.A logical unit will be placed on a single line if it fits.A simple carriage return in the input file is treated as a space. The occurrence of two consecutivecarriage returns (a blank line) is preserved in the output file. Three or more consecutive returns(two or more blank lines) result in two blank lines in the output file. Since all Bravo looks arediscarded by the scanner, paragraph leading done with looks is not preserved.For output files that contain fonts and faces (Press or Bravo) these additional rules apply:Comments are set in italics.The names of procedures are bold where they are defined.Reserved words and predeclared identifiers are in Font 1.Н'.ОfЯpНGОН хОbtsТrsrНґО^оТ∙Т√П;НґО](Т≤srТ≥П/НґО[─ТsrН хОX2tsrsrs tsНґОTЦrТ─ПPТ│НґОS<ТsrП!Н хОOМs НґОL·rП0НЇОIPТ─Т│П^НЇОG╗Т■П/Т∙П4НЇОFТгП7ТхП%НЇОA.pТНЇО<\tНЇО9 rТ┤ПQТ┬НЇО7fТ┴ПMТ┼НЇО5ЎТ НЇО0ЛtНЇО-²rТїП:Т╗П%НЇО+ЖТПBНЇО'сТ╔ПAТіНЇО&,ТНЇО" П:НЇО╩Т█П-Т▌П8НЇОТ╗ПOТ╘НЇОlТ╛ПHТґНЇОеТПMНЇОёТЫП4ТЗП(Н╛О(ТН╛ОґП8Н╛О2П9ДЇ К=ГZ ЮFormatter3Font 1 should be smaller than font 0. The fonts Helvetica 10 and Helvetica 8 work well inBravo mode. For press files, the formatter choses Helvetica 10 and 8 for portrait listingsand Helvetica 8 and 6 for landscape listings.In general there are no spaces before or after atoms containing only special characters. Exceptionsto this rule are as follows:A space or carriage return follows (but does not precede) a comma, semicolon, or colon.A space precedes a left square bracket when the bracket follows any of the keywordsRECORD, MACHINE CODE, PROCEDURE, RETURNS, SIGNAL, PORT, and PROGRAM.Spaces surround the left-arrow operator.The exclamation point (enabling) and equal-greater (chooses) operators are alwayssurrounded by spaces. This is also true for equal signs used in initialization and forasterisks used in place of variant record tags.Some arithmetic operators, depending on their precedence, are surrounded by spaces.The equivalent of two spaces are used for each level of indenting.StructureThe formatter determines the indenting structure of the program by the brackets that surround thebodies of compounds. The brackets include {}, (), [], BEGIN-END, DO-ENDLOOP, and FROM-ENDCASE.An attempt is made to maximize the amount of information on a page. For example, consider:Record: TYPE = RECORD [Record: TYPE = RECORDfield: Type,[field: Type];field: Type,field: Type,];In both cases, the structure is clear; it is indicated by the indenting, not the placement of thebrackets. The formatter generates the form on the left.The body of each compound, assuming it does not fit on a single line, is indented one nesting level.The placement of the brackets depends on the bracket and on its prefix and its suffix. Forexample, a loop statement has the following possible prefixes, brackets, and suffixes:PrefixesBracketsSuffixesFOR, WHILEDOOPENUNTIL, (empty)ENDLOOPENABLEThe following paragraphs contain a number of examples. They observe the following rules for theplacement of opening and closing brackets:The opening brackets {, [, FROM, and DO appear on the same line as their prefixes; BEGINstarts on a new line.If the remainder of the statement fits on a single line (with its closing bracket), it is placedthere, indented one level. Otherwise, all closing brackets except ] and } appear on lines bythemselves. If } is preceded by a semicolon, then it is also placed on a line by itself.ЪН'.ОfЯpНGОН╛ОbrТ┬Т┴ПMН╛О`vТіП+ТїП0Н╛О^оТП-НЇОZґТ■П(Т∙П<НЇОYТН╛ОV┼ТґТўПDН╛ОTТрТсП5Н╛ОRhurТururururururН╛ОOМП(Н╛ОMrТ4ПJТ5Н╛ОKкТвПWН╛ОJ#ТП/Н╛ОG╗ТМТНП9НЇОC├ТПBНЇО>ЁtНЇО;erТ■Т∙ПIНЇО9ҐТ┐П+vrvrvwrururururururНЇО8Т╩П8Т╪П"Н╛О4гvТ─uvuvН0;ТuvuН═О3 vТ─Н2)Н═О1yН2)ТН2)О/яН2)О.*НЇО*rТеП&ТфП;НЇО(`ТП8НЇО%Т└П?Т┘П%НЇО#jТуТжПKНЇО!цТПVН╛ОЧ╞ОtН"sОЧЭОtН0;ОЧ╨ОtН╛ОмurТ─uН"suН0;uН╛О&urН"suН0;uНЇОвrТ⌠П\Т■НЇО0ТП*Н╛О╣Т vrvrurur Т⌡uН╛О rТН╛О▓Т▒П`Н╛О КТ┬Т┴П4vrvrН╛ОDТ©vrП$ТюП$ pЇЩ>Г\ZFormatter4The statement following a THEN or ELSE is indented one level, unless it fits on the same line. THENis on the same line as its matching IF, and ELSE is indented the same amount as IF.IF bool THENIF bool THEN statementBEGINELSE {body}bodyENDELSEIF bool THEN {BEGIN statement;body statement}ENDThe labels of a SELECT (and its terminating ENDCASE) are indented one level, and the statements asecond level, unless they fit on the same line with the label.SELECT tag FROMcase => statement;case => long statement;ENDCASEEach compound BEGIN-END, DO-ENDLOOP, or bracket pair is indented one level. When the rules forIF and SELECT call for indenting a statement, a BEGIN is not indented an extra level.These rules are not exhaustive, but are intended to give the flavor of the formatter output.Formatter SwitchesSwitches allow you to modify command input. A command has the general formfile[/s] {file2[/s] . . .}where [] indicates an optional part and s is a sequence of switch specifications. A switchspecification is a letter, identifying the switch, optionally preceded by a '-' or '~' to reverse its sense.The valid switches areccompile input file after formattinggdon't close press file at end of input filehgenerate a press file (does not force ~t)kgenerate a two-column landscape press file (does not force ~t)ppause after formatting if there are errorsrterminate formatting and run the program contained in filetoverwrite input file with plain text formatted version (default)voverwrite input file with bravo looks using fonts 6 and 7zoverwrite input file with bravo looks using fonts 0 and 1Each switch has a default setting, The command sourcefile is equivalent tosourcefile/~c~g~h~k~p~rt~u~x~z if you use the standard defaults, i.e., the formatter onlygenerates a plain text file to replace the original source. Note that the "r" switch changes theinterpretation of file, which should name a subsystem.If the assignment of switch names does not seem too mnemonic, realize that with the /c switch, alladditional switches are passed to the compiler. For example,Н'.ОfЯpНGОНЇОbrТ┼ururП)Т▀uНЇО`vrТП$urururН╛О](urТ─vruН"─urТvrurvН═О[─uН"─urvН═ОYыvН═ОX2uН╛ОV┼uН"─urvrurvН═ОTЦuН"─rv Н═ОS<Н"─Н═ОQ■uНЇОNFrТ√ururП,Т≈НЇОL·ТП>Н╛ОIPurvruН═ОG╗vrv Н═ОFvrН═ОDZvН═ОB╡uНЇО?drТ┴ ururururП.Т┼ НЇО=╪urТurП#urНЇО:nТХТИПMНЇО5⌡pТНЇО2LrПKНЎО/яsНЇО-VrТРП(wr ТСП$НЇО+╞Т─ПKТ│srsrНЇО*ТНґО&╧sНеrП#НґО%sНеrП+НґО#jsНеrtrsrНґО!цsНеrП1trsrНґО sНеrП*НґОtsНеrП:НґОмsНеrП@НґО&sНеrП9НґО~sНеrП9НЇО0Т▄ Т█П%s rНЇО┬srТўП6Т╞НЇОАТ╨Т╩П1srНЇО:ТsrНЇО КТ┼П!Т▀П3srНЇОDТП< ЇЩ>Г\^Formatter5>Formatter Foo/cj-awould reformat Foo.mesa and then call>Compiler Foo/j-a.You can also change the default setting of any switch by using a global switch. Switches given withno sourcefile establish the default setting. Unless overridden or reset, that default applies to allsubsequent commands. See, for example, the multiple program Press output example below.Here is some information about the options:gIf a press file is being generated, it is not closed at the end of the current input file. It isexpected that another file in the command list will also be generating press file outputand a single press file will contain multiple input files. The name of the press file willbe that of the first to which press output is being generated. If the type of press file(landscape versus portrait) changes, the first will be forced closed and another press filewill be started. Be careful not to generate a press file larger than will be accepted byyour printer.v, z These switches cause the formatted version of the source file to contain bravo looks.The "z" switch is intended to be used on a standard Mesa Programming disk that hasHelvetica 10 and Helvetica 8 as fonts 0 and 1. The "v" switch uses fonts 6 and 7 andproduces output that is more convenient for including in documentation. Indenting ishandled slightly differently for bravo format output files. In plain text mode, indentationis done by a combination of tabs and spaces: the font is assumed to be fixed pitch andthe tab is assumed to be 8 times the width of a space. The z switch causes allindentation to be done with spaces only. For v, each level of indentation is indicated bya single tab.Examples:fooFormat foo using all the default switch settings (standard or established by a globalswitch).foo/-tkFormats foo into a two-column, landscape press file, leaving the original source unchanged./-tkg ProgA ProgB ProgC ProgD/-g Produces a two-column, landscape press file ProgA.press that contains listing of all fourprograms, each starting on a new page.The r (run) and p (pause) switches have identical semantics as in the compiler.Formatter FailuresThe message reporting a formatter failure has the following form:Н'.ОfЯpНGОНґОbsТНЇО^оrsr НґО[─srНЇОX2Т└Т┘П]НЇОV┼Т╣П4ТІП1НЇОTЦТяП(ТрП1НЇОQ■ТП+Н юОNFsН`rТ─П)Т│П8Н`ОL·ТєП)Т╔П/Н`ОJВТ П?Т⌡Н`ОIPТ╘П#Т╙П6Н`ОG╗Т≥П3Т П(Н`ОFТіТїП9Н`ОDZТtН юОAsТ─ЫxЬЪЗЪН`rЫЬЗТаП3ТбН`О?dТїП%Т╗П-Н`О=╪Т²П%Т·П0Н`О<Т╚Т╛ПFН`О:nТ─ПEТ│Н`О8фТ▐ Т░ПMН`О7ТБП-ТЦП"Н`О5xТ┤Т┬ПDН`О3пТНЇО0┌Н хО-3sН╛О*╦rТАsrП&ТБП%Н╛О)Н хО%бsН╛О#GrТ│srТ┌ПIН хОЬsТП!Н╛О}rТ▓Т⌠s rП"Н╛ОжТП&НЇО┤sr srПDoc>XferCounter.bravo .pressDRAFTThis tool for studying the behavior of Mesa programs counts the number of control transfers(XFERs) to a module and records the time spent executing in a module; it can also be used to gatherinformation on the flow of control between groups of modules. An XFER is the general controltransfer mechanism in Mesa. The following are all XFERs: procedure calls, returns from procedures,traps, and process switches.The system is implemented as a set of commands that can be executed from the Mesa Debugger, aroutine that intercepts all XFERs and collects statistics about them, plus a routine that interceptsconditional breakpoints for turning the XFER monitoring on and off. Existing Debugger commandsare used to specify where XFER monitoring is enabled, and additional commands are provided forcontrolling the counting of XFERs and outputting the results.This tool is intended to provide a global view of the behavior of a system. With this tool, a usercan identify modules that warrant closer study with other tools such as the Performance Monitor.ComponentsCountTool is the component of the tool that lives with user programs built on top of Alto/Mesa.This configuration contains one module: Counter. It contains the XFER trap handler and abreakpoint handler. CountTool must be loaded and started in the system it will monitor. Thismay be done by including CountTool in the client configuration whose control module importsand starts XferCountDefs.Counter or by executing the following command to the AltoExecutive:>Mesa CountTool ClientCountPackage is the component that lives as a tool in the Mesa Debugger. It implements thebasic commands required to enable XFER monitoring and to output measurement results.CountPackage must be loaded into the Debugger before its commands can be executed. It iseasiest to load it when installing the Debugger by executing the following command to the AltoExecutive:Н]Оg║pТiНІОc8qН]rТX Н-єqН7BrНІО]ШqН]r Н-єqН7BrНІОYqН]rН-єqН7Br НЭОSЛsrНЇОMqТFП2Н>ЁuНЇОFHrТжПQТв НЇОD═vrТ─П@Т│НЇОBЫТ╠ПBvrТ╡НЇОARТ┐Т└vrП,НЇО?╙ТНЇО<\Т█ПCТ▌НЇО:ЄТ╩vr Т╪П6НЇО9 Т≈Т≤vrП2НЇО7fТ═vrП<Т║НЇО5ЎТvrНЇО2pТ⌡Т°ПZНЇО0хТіПGТїНЇО+рw НЇО(└xrТ■ПDТ∙НЇО&эТыП(xrТз vrНЇО%5Т╟xrТ╠П$НЇО#▌ТґxrП9НЇО!ФТ xrТНЇО ? НґОПyТНЇО╒xrТ║Т╒ПHНЇОЗТ%Т& vrП.НЇОSxrТ╘ПMНЇО╛Т╡П2ТЁП,НЇО ЪJЭҐ=ГVEXfer Counting Tool2>XDebug CountPackage/lThe CountPackage creates a window through which all interactions with the tool take place.OperationThere are two modes of operation, plain and matrix. Plain mode (the default) simply records thetime spend in a module and the number of XFER to that module. Matrix mode is used to gatherinformation on the flow of control between groups of modules. Each module is a member of oneof 16 groups. A 16 by 16 matrix of counts and times is maintained by the Counter. The rows ofthe matrix are the groups of the source of the Xfer, the from group. The columns of the matrixare the groups of the destination of the Xfer, the to group.In plain mode, when XFER monitoring is enabled and a XFER occurs, the trap handler calculates thetime since the last XFER and adds that to the cumulative time for the current module. It thencalculates which module is the destination of the XFER and makes that the current module,incrementing its count. In matrix mode, the trap handler updates the appropriate element of thematrix. The XFER handler then completes the XFER, and the user program continues.The state of XFER monitoring can be controlled by two methods. The first is by setting aconditional break to be handled by the tool's breakpoint handler. The second is by calling theprocedures XferCountDefs.StartCounting and XferCountDefs.StopCounting.When the break handler intercepts a breakpoint, it checks to see if the breakpoint is conditional. Ifnot, the break handler proceeds to the Debugger. Otherwise, the state of XFER monitoring ischanged and program execution is resumed. A condition of zero turns XFER monitoring on; acondition of one toggles the state of XFER monitoring; a condition of two turns XFER monitoringoff. Any other condition has no effect.The procedures XferCountDefs.StartCounting and XferCountDefs.StopCounting providean alternative method of enabling XFER monitoring. These procedures may be called fromstatements in the user's program, or they may be called using the Debugger's interpreter.Since multiple processes may interact with each other, there is the concept of the tracked process. Ifthis process is not NIL, only those XFERs that are encountered during execution of the trackedprocess are counted; all others are simply resumed. If the tracked process process is NIL, then allprocesses contribute to the accumulated data.The CountPackage determines group membership by reading a file that associates groupnumbers with global frames. The easiest way to produce this file is to use the Debugger'sDisplay GlobalFrameTable command and then edit the file Debug.log. Append the desiredgroup number to the line for that module. If no group number is specified for a line, it goes in thegroup specified by the previous line. Modules not assigned group numbers are in group zero. Forexample:StringsB, G:173134B, gfi:33B 1group 1StringsA, G:173140B, gfi:32Bgroup 1StreamsC, G:173144B, gfi:31B 2group 2StreamsB, G:173150B, gfi:30Bgroup 2StreamsA, G:173154B, gfi:27Bgroup 2SegmentsB, G:173160B, gfi:26B 3group 3SegmentsA, G:173164B, gfi:25Bgroup 3OurProcess, G:173170B, gfi:24B 4group 4ЪНЇОfЯwТНGОНґОbyzyНЇО^оrТбxrП9ТцНЇОYыwНЇОV┼rТ²Т·ПMНЇОTЦТ⌡П%Т°vrП/НЇОS<Т√П=Т≈НЇОQ■Т∙Т√П?НЇОOМТ⌡П9yrТ°П"НЇОNFТП3yrНЇОJВТ├vrТ┤vrП(НЇОIPТ╦vrТ╧П&НЇОG╗ТЙТКvrП#НЇОFТ╔П9ТіП'НЇОDZТvrvrП!НЇОAТДvrП2ТЕНЇО?dТЇТ╦ПNНЇО=╪Т xrxrНЇО:nТ├Т┤П^НЇО8фТлП<Тм vr НЇО7ТюПEvrНЇО5xТїП&vrТ╗vr НЇО3пТП(НЇО0┌Т²xrxrТ·НЇО.зТРП!ТСvrП1НЇО-3ТПYНЇО)ДТ│П/Т┌П${rНЇО(=ТкТлqrvrП6НЇО&√Т║ПVqr НЇО$НТП-НЇО!цxrТПDНЇО ?ТЕПDТФНЇО╩yТ└ryryr Т┘НЇО7Т┐ПPТ└НЇОЁТ▀П2Т▄П/НЇО/НґО0yТвН4rТXНґО╛yТвН4rТXНґО(yТвН4rТXНґОєyТвН4rТXНґО yТвН4rТXНґО⌡yТвН4rТXНґО yТвН4rТXНґО⌠yТвН4rТXЪXЇL=Г\©┬Xfer Counting Tool3NonResident, G:173210B, gfi:23Bgroup 4Modules, G:173214B, gfi:22Bgroup 4Miscellaneous, G:173220B, gfi:21Bgroup 4MesaInit, G:173224B, gfi:20B 0group 0MesaDebug, G:173234B, gfi:17Bgroup 0Window and CommandsInteraction with the CountPackage is through its window. There are three subwindows: themessage subwindow, the form subwindow, and the log subwindow. Error messages and warningsare displayed in the message subwindow. Commands are invoked in the form subwindow. Alloutput is displayed in the log subwindow and written on Count.log. An illustration of thewindow during a sample session is shown in Figure 1.The elements of the form subwindow are explained below:Monitor: {off, on}Turns off/on the tools breakpoint handler. All conditional breakpoints will affect the stateof XFER monitoring when the monitor is on, and will behave like normal conditionalbreakpoints when it is off.Zero Tables!Zeros out all counts and times.Condition Breaks!Makes all non-conditional breakpoints into conditional breakpoints by adding the condition"1" to them.Print Tables!Displays all the statistics for each module in order of increasing global frame table index(gfi) for plain mode. In matrix mode, it displays the statistics for each nonzero element ofthe matrix. The output format of times is sec.msec:usec. May be aborted by typing^DEL.Print Sorted!Displays all the statistics for each module in order of decreasing time or decreasing numberof XFERs depending on the value of Sort by. May be aborted by typing ^DEL. Notallowed in matrix mode.Sort by: {count, time}When set to count, the Print Sorted command displays in order of decreasing numberof XFERs, otherwise it displays in order of decreasing time.Print Module!Displays the statistics for the module specified by Module. Not allowed in matrix mode.НЇОfЯwТНGОНґОbyТвН4rТXНґО` yТвН4rТXНґО_yТвП!Н4rТXНґО]▓yТвН4rТXНґО\yТвН4rТXНЇОWwТНЇОSиrТбxrП"ТцНЇОR"Т╔П2ТіП(НЇОPzТ╣П(ТІП1НЇОNсТмП8yrТнНЇОM,ТП4НЇОIщП7НЇОF▌yНґОC@rТ▓П/Т⌠П.НґОA≤ТзvrТшП,НґО?ЯТНЇО<╒yНґО9TrНЇО6yНґО2ІrТ▐ПZНґО1ТНЇО-юyНґО*rrТ╘П$Т╙П7НґО(йТ▒Т▓ПHНґО'#Т║П+yrТ╒НґО%|yrНЇО"-yТНґОчrТ┴П4Т┼П(НґО7ТўvryryТ╞rНґО░ТНЇОAyНґОРrТ▀ Т▄yryrП/НґОKТvrП5НЇОЭyНґОўrТ∙П4yr Т√Ъ$Їg=Г[єXfer Counting Tool4Module:Specifys the module to the Print Module command. It is either the module's globalframe table index (gfi), its global frame address (g), or its module name (if the currentconfiguration contains the desired module).Set Process!Tells the Counter to count only those XFERs that are executed by the specified process.An octal ProcessHandle as obtained from the Debugger's List Processes command isacceptable as input to this command. The default case is to track all processes.Process:Used by the Set Process command. It contains an octal ProcessHandle as obtainedfrom the Debugger's List Processes command. If Process is empty, all processes aretracked.Mode: {plain, matrix}When set to plain (default) the Counter functions as in Mesa 6.0. When set to matrixthe Counter records the flow from one group to another.Load Matrix!Using the current selection as a file name, reads the file to input group information.Show Group!Using the current selection as a group number, prints the names of the modules belongingto that group. May be aborted by typing ^DEL.Limitations1. Execution Speed: Xfer monitoring slows down the executions of a program considerably sinceextra processing is done on every XFER. As a result, interrupt processes that are triggered by clockswill run relatively more frequently; e.g. the keyboard process being interrupted by the display.2. Idle Loop Accounting: When no process is running, the Mesa Emulator runs in its idle loopwaiting for a process to become ready. This idle time is charged to the process that was lastrunning.3. Time Base: The time base available on the Alto is a 26-bit counter, where the basic unit of timeis 38 microseconds. Thus the counter turns over every 40 minutes, and no individual time greaterthan 40 minutes is meaningful. Total times are 32-bit numbers and will overflow after 340 minutes.4. Overhead Calculation: Due to implementation restrictions and timer granularity, some of theoverhead of processing an XFER trap is incorrectly assigned to the client program instead of theCountTool. As a result, times must be interpreted as only a relative measure of the time spent ina module.5. Counter Sizes: Counts are 32-bit numbers. The maximum total count is 4,294,967,295 XFERs!6. Memory Requirements: The CountTool requires seven pages of resident memory: two for itscode and five for its frames and tables. This may affect the performance of some systems that use aНЇОfЯwТНGОНЇОbyНґО^оrТ╪yТҐrП+НґО](ТЎПYНґО[─ТП+НЇОX2yНґОTЦrТ╙ xrvrП-НґОS<Т▒zrТ▓П!y r НґОQ■ТПQНЇОNFyНґОJВrТ╠y rТ╡ zrНґОIPТ┬y r yrТ┴НґОG╗НЇОD}yТНґОB%rТ∙yrП0Т√ yНґО@║rТП7НЇО=vyНґО;rТэПIТщНЇО7СyТ НґО5⌡rТ■П.Т∙П*НґО4ТП)yrНЇО/Уw НЇО,іrТёТєПKНЇО*ЪТ┤Т┬vrП@НЇО)WТйП`НЇО& Т╛П5ТґП(НЇО$aТф ТгПSНЇО"╨НЇОkТ┬ПWТ┴НЇОдТ╒П5ТёП+НЇОТ┘Т├ПQНЇОЗТ╣П<ТІП#НЇОSvrТЇПBНЇО╛xrТ▄ПDТ█НЇОТНЇОІТёП.ТєП*vrНЇОgТ⌠xrП2Т■НЇО юТ│П9Т┌П+ °Ї y=Г]▓Xfer Counting Tool5lot of memory, especially on the Alto.7. CountTool's break handler acts like a worry mode breakpoint; as a consequence, you may findyou cannot Quit from the Debugger after your session. Use the Kill Debugger command instead.Getting StartedOutlined below are the steps required for using the measurement tool.1. obtain the bcd's for CountTool and CountPackage. 2. install the CountPackage in the Mesa Debugger (version 6.0).3. start your program executing with the CountTool included.4. enter the Debugger and set conditional breakpoints to enable monitoring as desired.5. turn the break handler on by setting the Monitor parameter to on.6. proceed with program execution.7. return to the Debugger via control-swat or an unconditional breakpoint.8. display results with the Print commands.ЪНЇОfЯwТНGОНЇОbrП&НЇО^оТ█xzrТ▌ПPНЇО](Т┘ yrТ├yrНЇОX2wТНЇОTЦrПEНЇОQ■xrxrНЇОNFxrП$НЇОJВП)xr НЇОG╗ПVНЇОDZП,yr yrНЇОAП"НюО=╪ПJНЇО:nyr (Ї7=Г0ЛdXfer Counting Tool6Sample SessionThe following annotated listing of Debug.log and Count.log should give a fair idea of the use ofthe measurement tool. The Debugger was invoked by the Mesa Executive's Debug commandAlto/Mesa Debugger 6.0m of 5-Sep-80 12:0225-Sep-80 9:56You called?>SEt Root configuration: MesaExec>SEt Module context: MesaExec>Break Entry procedure: LoadNew Breakpoint #1. -- Count XFER involved withloading>Break Xit procedure: LoadNew Breakpoint #2.-- the Condition Breaks command will make these conditional breaks-- now interact with the CountPackage. Condition breaks and set the process>Proceed [Confirm]You called?-- now look at the results>--Test.map-- file containing group information-- now set mode to matrix and load group information using Load Matrix command>Proceed [Confirm]You called?-- now look at the matrix>Kill session [Confirm]Xfer Counter 6.0 of 19-Sep-80 9:5325-Sep-80 10:48Track process: 3647B-- ignore keyboard and interrupt keyConditionalized breaks-- Output of Print Tables command with mode = plainTotal Xfers 4,088Total Time 1.329:842 Gfi Frame Module #Xfers %Xfers Time %Time---- ------- ------------------ ----------- ------- ----------- ------ 1B 174164B Resident 12 .29 6:286 .47 3B 174030B DiskIO 869 21.25 583:996 43.91 4B 174000B Swapper 530 12.96 96:050 7.22 5B 173344B MDSRegion 538 13.16 200:367 15.06 7B 173314B BFS 1 .02 76 .00 10B 173304B Directory 80 1.95 38:900 2.92 11B 173270B DiskKD 2 .04 533 .04 13B 173260B Files 140 3.42 15:392 1.15 15B 173254B FSP 100 2.44 15:468 1.16 16B 173240B LoadState 97 2.37 105:384 7.92 22B 173214B Modules 96 2.34 35:471 2.66 23B 173210B NonResident 3 .07 457 .03 25B 173164B SegmentsA 74 1.81 17:945 1.34 26B 173160B SegmentsB 89 2.17 13:487 1.01 27B 173154B StreamsA 55 1.34 10:629 .79 30B 173150B StreamsB 44 1.07 8:115 .61 31B 173144B StreamsC 55 1.34 10:629 .79 32B 173140B StringsA 89 2.17 9:525 .71 33B 173134B StringsB 19 .46 3:924 .29 35B 173124B AlFont 176 4.30 21:107 1.58ЪНЇОfЯwТНGОНЇОbТX НЇО_rП#yryrП&НЇО]▓ПHyrНЇОZ┼yТвП*НЇОYНЇОUЩ НЇОTyП!НЇОRУНЇОQqП/ryryvrТX НЇОOМНЇОNiyТвП,НЇОLЕrТXyТвrТXП+НЇОKayrП'НЇОIщyТвНЇОHY НЇОFуrТXНЇОEQy НЇrП$НЇОCмyТвrТXyТвrНЇОBIyНЇО@е НЇО?ArТXНЇО=╪yТвНЇО90П#НЇО7╛НЇО4єНЇrТXП$НЇО3 yТвНЇО.■rТXyТв rТXyТвНЇО-НЇО+▄НЇО*ПFНЇО(└ПFНЇО'ПFНЇО%|ПFНЇО#ЬПFНЇО"sПFНЇО ОПFНЇОkПFНЇОГПFНЇОcПFНЇОъПFНЇО[ПFНЇОвПFНЇОSПFНЇОоПFНЇОKПFНЇОгПFНЇОCПFНЇО©ПFНЇО ;ПFНЇОЇПFНЇО 3ПF NЇ Л;I^Xfer Counting Tool7 36B 173104B AltoLoader 237 5.79 29:070 2.18 40B 173100B BcdOperations 153 3.74 16:421 1.23 45B 172720B LoaderCore 516 12.62 74:256 5.58 47B 172660B StreamIO 23 .56 2:057 .15 50B 172650B SystemDisplay 82 2.00 13:830 1.03 54B 170274B MesaExec 8 .19 457 .03Ignored Xfers 98Ignored Time 309:943-- Output of Print Sorted command with Sorted by = countTotal Xfers 4,088Total Time 1.329:842 Gfi Frame Module #Xfers %Xfers Time %Time---- ------- ------------------ ----------- ------- ----------- ------ 3B 174030B DiskIO 869 21.25 583:996 43.91 5B 173344B MDSRegion 538 13.16 200:367 15.06 4B 174000B Swapper 530 12.96 96:050 7.22 45B 172720B LoaderCore 516 12.62 74:256 5.58 36B 173104B AltoLoader 237 5.79 29:070 2.18 35B 173124B AlFont 176 4.30 21:107 1.58 40B 173100B BcdOperations 153 3.74 16:421 1.23 13B 173260B Files 140 3.42 15:392 1.15 15B 173254B FSP 100 2.44 15:468 1.16 16B 173240B LoadState 97 2.37 105:384 7.92 22B 173214B Modules 96 2.34 35:471 2.66 26B 173160B SegmentsB 89 2.17 13:487 1.01 32B 173140B StringsA 89 2.17 9:525 .71 50B 172650B SystemDisplay 82 2.00 13:830 1.03 10B 173304B Directory 80 1.95 38:900 2.92 25B 173164B SegmentsA 74 1.81 17:945 1.34 27B 173154B StreamsA 55 1.34 10:629 .79 31B 173144B StreamsC 55 1.34 10:629 .79 30B 173150B StreamsB 44 1.07 8:115 .61 47B 172660B StreamIO 23 .56 2:057 .15 33B 173134B StringsB 19 .46 3:924 .29 1B 174164B Resident 12 .29 6:286 .47 54B 170274B MesaExec 8 .19 457 .03 23B 173210B NonResident 3 .07 457 .03 11B 173270B DiskKD 2 .04 533 .04 7B 173314B BFS 1 .02 76 .00Ignored Xfers 98Ignored Time 309:943-- Output of Print Sorted command with Sorted by = timeTotal Xfers 4,088Total Time 1.329:842 Gfi Frame Module #Xfers %Xfers Time %Time---- ------- ------------------ ----------- ------- ----------- ------ 3B 174030B DiskIO 869 21.25 583:996 43.91 5B 173344B MDSRegion 538 13.16 200:367 15.06 16B 173240B LoadState 97 2.37 105:384 7.92 4B 174000B Swapper 530 12.96 96:050 7.22 45B 172720B LoaderCore 516 12.62 74:256 5.58 10B 173304B Directory 80 1.95 38:900 2.92 22B 173214B Modules 96 2.34 35:471 2.66НЇОfЯwТНGОНЇОbyТвПFНЇО` ПFНЇО_ПFНЇО]▓ПFНЇО\ПFНЇОZ┼ПFНЇОYНЇОW│НЇОQqrТXyТв rТXyТвНЇОOМНЇОNiНЇОLЕПFНЇОKaПFНЇОIщПFНЇОHYПFНЇОFуПFНЇОEQПFНЇОCмПFНЇОBIПFНЇО@еПFНЇО?AПFНЇО=╪ПFНЇО<8ПFНЇО:ЄПFНЇО90ПFНЇО7╛ПFНЇО6(ПFНЇО4єПFНЇО3 ПFНЇО1°ПFНЇО0ПFНЇО.■ПFНЇО-ПFНЇО+▄ПFНЇО*ПFНЇО(└ПFНЇО'ПFНЇО%|ПFНЇО#ЬПFНЇО"sНЇО ОНЇОъrТXyТв rТXyТвНЇО[НЇОвНЇОSПFНЇОоПFНЇОKПFНЇОгПFНЇОCПFНЇО©ПFНЇО ;ПFНЇОЇПFНЇО 3ПFЪ Ї Л:и^ЫXfer Counting Tool8 36B 173104B AltoLoader 237 5.79 29:070 2.18 35B 173124B AlFont 176 4.30 21:107 1.58 25B 173164B SegmentsA 74 1.81 17:945 1.34 40B 173100B BcdOperations 153 3.74 16:421 1.23 15B 173254B FSP 100 2.44 15:468 1.16 13B 173260B Files 140 3.42 15:392 1.15 50B 172650B SystemDisplay 82 2.00 13:830 1.03 26B 173160B SegmentsB 89 2.17 13:487 1.01 31B 173144B StreamsC 55 1.34 10:629 .79 27B 173154B StreamsA 55 1.34 10:629 .79 32B 173140B StringsA 89 2.17 9:525 .71 30B 173150B StreamsB 44 1.07 8:115 .61 1B 174164B Resident 12 .29 6:286 .47 33B 173134B StringsB 19 .46 3:924 .29 47B 172660B StreamIO 23 .56 2:057 .15 11B 173270B DiskKD 2 .04 533 .04 23B 173210B NonResident 3 .07 457 .03 54B 170274B MesaExec 8 .19 457 .03 7B 173314B BFS 1 .02 76 .00Ignored Xfers 98Ignored Time 309:943Matrix loaded-- Output of Print Tables command with mode = matrixTotal Xfers 3,834Total Time 871:004From -> To #Xfers %Xfers Time %Time---- --- ----------- ------- ----------- ------ 1 -> 1 2 .05 114 .01 1 -> 2 1 .02 114 .01 1 -> 3 4 .10 266 .03 2 -> 1 1 .02 419 .04 2 -> 2 542 14.13 110:756 12.71 2 -> 4 126 3.28 17:487 2.00 2 -> 5 87 2.26 11:201 1.28 2 -> 6 7 .18 342 .03 2 -> 10 53 1.38 17:221 1.97 3 -> 1 4 .10 228 .02 3 -> 3 179 4.66 37:719 4.33 3 -> 4 64 1.66 5:829 .66 3 -> 6 13 .33 2:247 .25 3 -> 10 1 .02 38 .00 4 -> 2 124 3.23 19:240 2.20 4 -> 3 61 1.59 6:705 .76 4 -> 4 1,105 28.82 264:795 30.40 4 -> 6 87 2.26 16:725 1.92 4 -> 7 9 .23 1:790 .20 4 -> 9 8 .20 5:486 .62 5 -> 2 82 2.13 13:563 1.55 6 -> 2 7 .18 495 .05 6 -> 3 14 .36 2:057 .23 6 -> 4 87 2.26 27:089 3.11 6 -> 6 207 5.39 54:330 6.23 6 -> 7 36 .93 7:658 .87 6 -> 10 12 .31 1:066 .12 7 -> 4 9 .23 2:552 .29 7 -> 6 37 .96 5:067 .58НЇОfЯwТНGОНЇОbyТвПFНЇО` ПFНЇО_ПFНЇО]▓ПFНЇО\ПFНЇОZ┼ПFНЇОYПFНЇОW│ПFНЇОUЩПFНЇОTyПFНЇОRУПFНЇОQqПFНЇОOМПFНЇОNiПFНЇОLЕПFНЇОKaПFНЇОIщПFНЇОHYПFНЇОFуПFНЇОEQНЇОCмНЇО?AНЇО<8rТXyТв rТXyТв НЇО:ЄНЇО90НЇО7╛П:НЇО6(П:НЇО4єП:НЇО3 П:НЇО1°П:НЇО0П:НЇО.■П:НЇО-П:НЇО+▄П:НЇО*П:НЇО(└П:НЇО'П:НЇО%|П:НЇО#ЬП:НЇО"sП:НЇО ОП:НЇОkП:НЇОГП:НЇОcП:НЇОъП:НЇО[П:НЇОвП:НЇОSП:НЇОоП:НЇОKП:НЇОгП:НЇОCП:НЇО©П:НЇО ;П:НЇОЇП:НЇО 3П:ЪТЇ Л:и^ЩXfer Counting Tool9 7 -> 7 759 19.79 221:932 25.48 9 -> 4 11 .28 647 .07 10 -> 2 59 1.53 9:944 1.14 10 -> 3 1 .02 152 .01 10 -> 6 12 .31 3:543 .40 10 -> 10 23 .59 2:171 .24Ignored Xfers 396Ignored Time 673:569ЪНЇОfЯwТНGОНЇОbyТвП:НЇО` П:НЇО_П:НЇО]▓П:НЇО\П:НЇОZ┼П:НЇОW│НЇОUЩЪіЇT20╣ы5`(Le`(┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┴ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЭ┬┬┬""#щоЪЪ▐ЪЪЪЪЪ▐ЬЪЪ?В▐ЬЪЪЬЦЪЬЪ?ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЧ"""""#щЇЪЪwЪЪ©ЪЪwВЧъГwВЪВ]ЪВ}ъЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЧ"""┬┬┴КЎ4Ъ~7S4ЪЖ▌ЪвwВЦOВYЪВъЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЭ┬┬┬┬┬┴В с}вMҐсOУt?ВgЬщ7ЬуЪЖw?ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЭ┬┬┬""#В╪}в]╪7УvЪВ■?At7UЪЫwwъЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЧ"""""#КҐВЪ}в]ҐВЪwСvЪВВЪ_wВMЪЪВъЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЧ"""┬┬┴щҐвЪuж]╣вЪwВvЪВwВ]7В]ЪВuъЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЭ┬┬┬┬┬┴щЎ7Ъ▌9]н7Ъ▐xЪ▌Ъа▐ЬЦOЬЦЪЬВ▌?ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЭ┬┬┬""#ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪВЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЧ"""""#ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЧ"""┬┬┴ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЭ┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴Ъ┬┬┬""#│"""""#│"""┬┬┴│┬┬┬┬┬┴ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪ│┬┬┬""#│"""""#│"""┬┬┴Ъ┬┬┬┬┬┴┬┬┬""#"""""#─Ъ─"""┬┬┴─├Ъ`ю@8─┬┬┬┬┬┴IЪ─@D──┬┬┬""#9c·9`Бi▌XЮ1a8@@Е█9Ц▌X√8д▌"""""#E░┬E▒·іeI▒D@AS─▒d≥E%"""┬┬┴E┬EўE90@AQ─▒DQ|Ф┬┬┬┬┬┴E┬EaўAI@AQ─▒DPA%┬┬┬""#E┴EўAI▒DES░▒DPE$▒"""""#9├9Б0nн@Ю=a8@8ДM`▌D░8ТN"""┬┬┴Ъ@┬┬┬┬┬┴ Ъ┬┬┬""#Ъ`"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""# ЪЪЪю─"""┬┬┴ Пp─88?ЪЪЪю──┬┬┬┬┬┴@@DDOЪЪЩю─@┬┬┬""#XЕ·CЦ└V9g─@Е·8я@Е·d@Lq╨≤@Ц∙8@"""""#d&HD≥DY ▓9HE19H■DKў╨mю─÷D@"""┬┬┴D$HC▒С▒ H}H└KН╨Мю─∙|@┬┬┬┬┬┴@$HD▒└ A─▀Н╨Мю─∙@0┬┬┬""#@$ID≥@ @E E0E ▓─Kў╡М─░∙D@"""""#@$FCжЦ└ ─8Д8я8ДaLqйНL`∙8@"""┬┬┴OЪЪЪд@┬┬┬┬┬┴ OЪЪЪх@┬┬┬""#?ЪЪЪю─"""""#"""┬┬┴┬┬┬┬┬┴?ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪ─ЪЪЪЪЪЪЪЪЪЪЪЭ┬┬┬""# ─"""""# ─"""┬┬┴ ю$@┤─ Ю┌|Ю┬┬┬┬┬┴@$@┬─@── F┬┬┬""#XЕ·Ё█DC└&н5┬П╛qгp─ ▌8Ц▌F """""#d&HЄSDDD&яM┤"@╡┼(╒┬─ QEQ┼ `"""┬┬┴D$HЄQDGд&яE─Ў@"┼≤`─ ДQAСJ░┬┬┬┬┬┴@$HTQDD%QE─═@ ┼─ A┌_┬┬┬""#@$ITSLD@%QM1┬╒H ┼(╒┬ EQB!"""""#@$FS█4C└%N4я┤0 qгp─ 8Ц▌┌ Ю"""┬┬┴ ──┬┬┬┬┬┴ ─┬┬┬""# ─"""""# ─"""┬┬┴?ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪ─ЪЪЪЪЪЪЪЪЪЪЪЭ┬┬┬┬┬┴┬┬┬""#"""""#ЪЪъю """┬┬┴?ЦЪъю @ 9Ю┬┬┬┬┬┴OШЪЪю@E┬┬┬""#8с─J{о@SXДD@Ц ЁXДDAc∙▌Ea"""""#E4DI╩Їы─Т┬d"└A⌠Є┬d"└9■UQE▒"""┬┬┴EдK╩гш─S┬D!A▒Ё┬D!UtQE┬┬┬┬┬┴E▀╩Їш─T┬@!A▒T┬@!JE┬┬┬""#E4@I╩Їш─T┴@"└A⌠T┴@"─EJ4M░"""""#8с└J{цш▄Sф@$D|ЦмSф@$D9┼т5a"""┬┬┴KЪЪЪд┬┬┬┬┬┴KЪЪЪх┬┬┬""#;ЪЪЪю"""""#"""┬┬┴┬┬┬┬┬┴Ъ┬┬┬""#│"""""#│"""┬┬┴│┬┬┬┬┬┴ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪ│┬┬┬""#│"""""#│"""┬┬┴Ъ┬┬┬┬┬┴┬┬┬""#FЮЮЦ─Ю8"""""#I$@D"""┬┬┴┬9`9·9`0 √ю┬┬┬┬┬┴E░EHE░PxДYЕ@1┬┬┬""#}EH}P xяy@я"""""#┬AEHA░ @"""┬┬┴HEE4IE Y@D┬┬┬┬┬┴H98тF9Ю нЦ√Ц─А8┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#·ЮЦ─@"""""#P@0ю0"""┬┬┴P√юQ@P┬┬┬┬┬┴·ДYЕ@A┬┬┬""#xяy@A"""""#@@"""┬┬┴Y@@┬┬┬┬┬┴нЦ√Ц─}Я|┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#"""┬┬┴┬┬┬┬┬┴┬┬┬""#"""""#ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЧ"""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""ЪНЪОЪЭwЩОЗLeReport on file: Fixed60m.rpt1 25-Sep-80 15:54:56Numb Originator Subsystem Subject er 490 Murray Binder Compiler doesn't check Defs for unEXPORTED exports 650 Johnsson Binder Packed bit on MT Records not set 801 Murray Binder Unbound procedure vs. Binder /r 1169 Wick Binder Configurations Specifying List of Control Modules 2039 Murray Binder Abort For ^C After Error 3128 Olmstead Binder Error messages re: different versions 4038 Evans Binder Lock released once too often when zap target bcd 4250 Knutsen Binder Issue Warning if two /c items 4416 Murray Binder Which module can't be packed 4478 LNelson Binder Binder under Tajo 4502 BLyon Binder 'IMPORT' instead of 'IMPORTS' in a CONFIG blew the binder up 4514 Knutsen Binder Copying code to bcd w/ "code" gives "Ref'd in diff versions" 4593 Luniewski Binder Output files incorrectly chosen 4656 mbrown Binder switch syntax: "bind /c foo" vs. "bind foo/c" 4658 Johnsson Binder Command line '; eats next char 4676 LNelson Binder Binder patches for Star 4765 Newman Binder "Foo.run/r" puts "Foo.run/" in Com.cm 4766 Newman Binder "Foo.image/r" doesn't work 4924 Newman Binder Fails to pause after syntax error 5392 Luniewski Binder Unimplemented command line args not detected 5393 Luniewski Binder Command line overriding of Directory statements 5727 LNelson Binder Fatal Binder Error: 1015B 5842 LNelson Binder LongBinder hung on config that standard binder handled OK 5885 Johnsson Binder Passing LINKS: CODE to pre-bound Config. 5887 Marzullo Binder binding packaged code with code copy 5950 Smokey Binder Fatal Binder ERROR 792 McJones Compiler Break Entry with DO as first statement 911 McJones Compiler Frames lost from UNWIND 1034 Murray Compiler Help on interupt routines 1969 Redell Compiler Bad Fine-grain Table 2068 Murray Compiler Poor Code For a+b*c 2622 Howard Compiler Fatal compiler error, Pass 5, 267601B 2858 Morrison Compiler Bad code generated for an INLINE (RXLPL) causes AddressFault 3335 Newman Compiler Doc: Pitfalls in allocating bound variants from a heap 3653 MBrown Compiler Error message for expressions in extractors 3660 Sweet Compiler bounds checking strings 3797 Howard Compiler RETURN WITH ERROR in ENTRY INLINE does wrong thing 4351 Guyton Compiler Short Pointer code generated from LONG DESCRIPTORS 4464 Tanaka.ES Compiler Subrange type in Defs gives bogus results 4537 McJones Compiler Zero-size field in M.D. record with explicit field positions 4547 Levin Compiler Bad FGT entry 4608 Hamilton Compiler ALL[ALL bombs pass 5 4657 Schwartz Compiler Compiler hangs in pass 5 when null EXITS clauses 4681 maxwell Compiler Crash in pass 5 4742 mitchell Compiler fatal, pass 5, variant record element compare w/nil checking 4774 ayers Compiler Error Messages' Construction 4899 Sweet Compiler Constant Table: zero length constants entered in the table 4941 Newman Compiler Doc: ABORTED totally undocumented 4956 McJones Compiler Extra FREE for large result record in FOR loop expression 4997 Swinehart Compiler Machine Dependent Records Bug 5112 AWells Compiler Bad code generation for array initialization 5114 AWells Compiler Internal stack overflow in recursive type declaration 5148 Luniewski Compiler Fatal compiler error pass 5 5151 Murray Compiler FOR Clause Problem - long variable and constant bounds 5172 Nelson Compiler Variant record defaults 5182 Knutsen Compiler Comparing expr to field of result of inline blows up 5215 Newman Compiler Type mismatches involving zone.NEW give poor error messages 5221 AWells Compiler Lack of defaults for declared return variables 5231 Wyatt Compiler Fatal from call on an INLINE procedure 5264 LStewart Compiler a, b: DESCRIPTOR _ [NIL,0] => "Multiple init w/ptr" 5276 Levin Compiler CV and ML addresses 5281 Newman Compiler Confused about compile-time constants & subrange types 5294 schmidt Compiler NEW of extremely large arrays 5298 Artibee Compiler OptCatchPhrase on WaitStmt sometimes mandatory 5324 Newman Compiler Can't zone.NEW for objects with non-constant size 5337 AWells Compiler Compiler dropping into the debugger in pass 5 5343 Levin Compiler @constructor gives fatal error 5385 Ludolph Compiler LOOP in loopexitsclause of inner loop repeats inner loop 5405 AJM@MIT-ML Compiler Multi-module MONITOR 5415 Daniels Compiler Fatal compiler error after ill-formed DIRECTORY clause 5417 Marzullo Compiler The same temporary location is assigned twice in a loop. 5424 Fay Compiler StackModelling Error in long, zero-based IN tests 5488 Knutsen Compiler MachDepRec complains of gaps НО_─П0НО]ПjНО[иПjНОYOПjНОXПjНОVуПjНОU≤ПjНОT[ПjНОSПjНОQАПjНОPєПjНОOgПjНОN*ПjНОLМПjНОK╟ПjНОJsПjНОI6ПjНОGЫПjНОF╪ПjНОEПjНОDBПjНОCПjНОAхПjНО@▀ПjНО?NПjНО>ПjНО<тПjНО;≈ПjНО:ZПjНО9ПjНО7ЮПjНО6ёПjНО5fПjНО4)ПjНО2ЛПjНО1╞ПjНО0rПjНО/5ПjНО-ЬПjНО,╩ПjНО+~ПjНО*AПjНО)ПjНО'гПjНО&┼ПjНО%MПjНО$ПjНО"сПjНО!√ПjНО YПjНОПjНОъПjНО╒ПjНОeПjНО(ПjНОКПjНОўПjНОqПjНО4ПjНОВПjНО╨ПjНО}ПjНО@ПjНОПjНО фПjНО┴ПjНОLПjНО ПjНОрПjНО∙ПjНОXПjНОПjНОчПjНО║ПjНОdПjНО'Пj>qЖGО`Ґ<5492 McJones Compiler Catch phrase should not be allowed on RETURN WITH ERROR 5546 LStewart Compiler Floating point compare to zero code generator 5614 Newman Compiler Mainline code local variables allocated in global frame 5622 Newman Compiler Type mismatch for PROC RETURNS [UNCOUNTED ZONE](or MDSZone) 5687 Newman Compiler Bad code for record constructor containing proc calls 5689 Forrest Compiler Long pointer to Packed ARRAY of >4K bits generates bad code 5710 Newman Compiler StackModelingError, pass 5 from LONG CARDINAL loop iteration 5720 Alfvin Compiler NIL as an acceptable ZONE value 5754 Daniels Compiler Fatal System Error (Punt) in Pass 5 5783 Swinehart Compiler Compiler loops in pass 5 with nil-checking on 5805 Swinehart Compiler Code generation bug -- long pointers 5846 Sweet Compiler [] _ ERROR SigReturnsValues; 1161 Morrison Debugger Command to Redisplay Uncaught Signal Messages 2155 Karlton Debugger Indirect Type-in For DebugWindow 2191 Johnsson Debugger p%FileName$Type fails 2432 Schwartz Debugger Doc: Cursor actions on tiny windows need documenting 2455 Schwartz Debugger Doc: >> prompt not documented 2460 Schwartz Debugger Doc: Some finepoints 2531 malasky Debugger Doc: Find Variable vs Search Context 2598 Selly Debugger Doc: Set Octal Context examples;Frame$var 2618 CharliLevy Debugger Display Stack source listing in error 2767 Purvy Debugger Doc: Reporting debugger problems 2910 charnley Debugger can't break at entry 3047 beard Debugger Debugger's unawareness of new source file 3182 olmstead Debugger Doc: conditional breakpoints 3410 Sandman Debugger PerfMonitor and XferCounter trap handlers and NOOPs 3456 Murray Debugger -1,-1 from Trace All Xits 3610 Birrell Debugger Doc: Going into Swat and overwriting Swatee 3662 Birrell Debugger Attach Image to use current load state 3663 Birrell Debugger Doc: Ascii read increments start address wrong 4020 Newman Debugger Doc: Some variables print out followed by "^R" 4160 LNelson Debugger Condition breaks vs subranges 4437 Murray Debugger process not bound 4445 Levin Debugger Debugger frame trouble 4525 Freier Debugger Display of variable of type PROCESS 4564 Kayashima Debugger Xdebug Hangs when Move or Grow sized window 4598 Hamilton Debugger Doc: Attach Symbols 4614 Kayashima Debugger Stripping Bravo Trailers 4633 mbrown Debugger Confusion about contexts 4655 mbrown Debugger Attach Mesa Source command 4672 Gobbel Debugger Debugger bitmap goes away sometimes if Edit is used. 4680 morris Debugger Debugger crash 4732 birrell Debugger Incorrect handling of multiple instances of modules 4741 Wyatt Debugger COremap bug 4743 Levin Debugger Lockup while repainting windows 4745 Murray Debugger Can't install Internal Debugger 4757 Newman Debugger Displaying arguments of Signaller.ErrorList goes to // mode 4759 Newman Debugger Fails to find symbols in files retrieved with FileTool 4761 Newman Debugger Misleading error message from Display Frame 4764 Newman Debugger Spurious "...is not a valid field selector" 4776 Murray Debugger 1001 while trying to Kill 4777 Murray Debugger context mixup 4783 ayers Debugger Debuggers erxtra-memory bitmap space 4789 ayers Debugger temp>xdebug.image Intall problems 4791 Murray Debugger Bound OVERLAID variants 4804 Levin Debugger Debugger bootloading: NIL PuntInfo gives PointerFault 4808 Levin Debugger Imported LONG DESCRIPTOR 4824 Newman Debugger Interpreter doesn't know size of UNSPECIFIED 4825 Newman Debugger Interpeting "array[Type[value]] gives uncaught signal 4827 Newman Debugger Enumerated values not found 4839 birrell Debugger Clear All Traces missing 4843 Newman Debugger List Breaks says nothing if no breaks set 4844 Newman Debugger ATtach Conditon command rejected 4851 Cattell Debugger Doc: No [non-wizard] way to get debugger to redisplay SIGNAL 4858 McGregor Debugger Debugger Inline eval bug 4864 Cattell Debugger NotRelocated SIGNAL from debugger on call to user routine 4869 Johnsson Debugger CL? doesn't list all options 4873 Johnsson Debugger ? for unknown PROCEDURE 4874 Karlton Debugger Will not display Ascii.NULs 4875 Sweet Debugger Clear Break # 4877 Sweet Debugger Display Break # 4880 Malasky Debugger ^Nvalidate cache command 4887 Newman Debugger Missing command "CLear Module" ?? 4889 Newman Debugger ATtach Expression to nonexistent break => no error msg 4890 Newman Debugger LIst Breaks doesn't display attached expressions... 4894 MBrown Debugger breakpoint set on "BEGIN" of proc body smashes entry break? 4916 Newman Debugger "Break ?" shows invalid options 4918 Newman Debugger "CLear ?" leaves some options out НО_─ПjНО^CПjНО]ПjНО[иПjНОZ▄ПjНОYOПjНОXПjНОVуПjНОU≤ПjНОT[ПjНОSПjНОQАПjНОPєПjНОOgПjНОN*ПjНОLМПjНОK╟ПjНОJsПjНОI6ПjНОGЫПjНОF╪ПjНОEПjНОDBПjНОCПjНОAхПjНО@▀ПjНО?NПjНО>ПjНО<тПjНО;≈ПjНО:ZПjНО9ПjНО7ЮПjНО6ёПjНО5fПjНО4)ПjНО2ЛПjНО1╞ПjНО0rПjНО/5ПjНО-ЬПjНО,╩ПjНО+~ПjНО*AПjНО)ПjНО'гПjНО&┼ПjНО%MПjНО$ПjНО"сПjНО!√ПjНО YПjНОПjНОъПjНО╒ПjНОeПjНО(ПjНОКПjНОўПjНОqПjНО4ПjНОВПjНО╨ПjНО}ПjНО@ПjНОПjНО фПjНО┴ПjНОLПjНО ПjНОрПjНО∙ПjНОXПjНОПjНОчПjНО║ПjНОdПjНО'Пj LqЖGО`ҐD4950 Hayes Debugger FileTool, PupAndFTP won't install manually in Int. Debugger 4963 Newman Debugger DisplayStack-source: clobbers editable window 4966 Newman Debugger "Trace ?" displays invalid options 4979 Frankel Debugger Symbol table reset infinite loop 5014 Newman Debugger DisplayStack + "?" leaves some options out 5027 Newman Debugger Initial position of windows shouldn't be overlaid 5028 Newman Debugger Interpreter won't display variables of type MDSZone 5046 Murray Debugger Octal Read hangs 5119 Sapsford Debugger ARRAY[interval] does not account for bias 5120 birrell Debugger Re-setting breaks 5131 MBrown Debugger Doc: what does output of the interpreter's ? operator mean? 5143 kolling Debugger Doc: Resetting symbol table 5176 JEllis Debugger Resetting Symbol Table vs Find Variable 5225 MBrown Debugger Display Module loses track of who is in the window 5228 Murray Debugger AScii Read should check Ctl-DEL 5229 Murray Debugger Garbage PC gives last PROCEDURE 5232 kolling Debugger source window selections, breakpoints, etc. 5244 Newman Debugger Named return values vs. exit breaks 5251 Murray Debugger PC to PROC mixup 5284 Newman Debugger "size mismatch" for Display Queue of CONDITION variable 5285 Newman Debugger Display Queue of MONITORLOCK => "100000B is invalid Process" 5286 Newman Debugger Display Queue of octal number fails 5299 Newman.ES Debugger Interpreter: subrange assignment error 5301 Murray Debugger PC mixup after clearing break 5302 Murray Debugger 47201 from Set Module Context (ambigious) 5315 Murray Debugger SourceWindow: context mixup 5328 Murray Debugger Display GlobalFrameTable 5364 JEllis Debugger No response to $ 5365 JEllis Debugger Interpreted relational expression produces Uncaught Signal 5384 Daniels Debugger Falling into // mode from Interpreter 5389 morris Debugger Breakpoint not found. 5484 Daniels Debugger Incorrect printing of variant records 5695 McJones Debugger Spurious question mark for value of large cardinal subrange 5742 Cattell Debugger allows attaching condition to non-existent breakpoint 5863 Israel Debugger Relative string 5883 Stewart Debugger PACKED ARRAY printing 5910 israel Debugger Relative array descriptors. 1823 Hamilton Ether FTPtool: no filstats 2092 Malasky Ether ChatTool: Should Attach Or Log In 2438 Schwartz Ether FileTool: behaves strangely when opened a second time. 2558 LNelson Ether FileTool: close connection logic is defective. 2766 Hamilton Ether FTPtool: "IFS full" funnies 2880 Clemons Ether FileTool: Closes connection unnecessarily 2906 israel Ether Pup: FTP: Slow on Dorado 3626 Murray Ether FTP: sending mail 3863 Murray.PA Ether Fetch: Make it more like FTPtool 3900 Murray Ether FTP: UNWIND from FTPEnumerate/retrieve 3987 Sapsford Ether FTP: TimeExtras.PackedTimeFromString vs StringBoundsFault 4131 Levin Ether FTP: FTPServers.config 4174 Hamilton Ether FileTool: deletion fails 4352 Karlton Ether FTP: FTPAltoFile.PreProcessFile does a blind ReleaseFile 4444 Schmidt.PA Ether FTP: FTPInventoryDumpFile needs create date parameter 4456 Birrell Ether Pup: FTP: Recompile packages to fix long return record bug 4499 Murray Ether FTP: FTPTransferFile doesn't pass through the creation date 4544 birrell Ether FTP: FTPRetrieve hangs until timeout on a "no" mark 4550 Levin Ether FileTool: "delete" bugs 4552 Birrell Ether Pup: ByteStream timeout 4590 birrell Ether FileTool: returns slowly if the client stops an enumeration 4612 Hamilton Ether FileTool: shift col.2 left; move "verify" 4763 Newman Ether FTP: Forgetting to call IdNxtRejRecip => disaster 4809 Levin Ether FileTool: Local Delete: error message is misleading 4904 Levin Ether FileTool: fails to restore command buttons 5005 birrell Ether Pup: 2 sec delay creating Byte Streams 5062 kolling Ether Pup: DriverDefs.debugPointer 5093 Murray Ether Pup: NameLookup vs dying nets 5098 Murray Ether Pup: EthernetDriver priority 5132 MBrown Ether FileTool: does not set creation date properly 5152 Murray Ether FTP: TimeExtras: zone screwup 5195 birrell Ether FileTool: window size 5198 birrell Ether FTP: make single config available with everything 5236 Newman Ether FileTool: obsolete free page count 5527 Newman Ether FIleTool: treat empty "source" field as "*" 1230 Judd Other DOC: Examples 2063 Ayers Other Perf. Monitor: Improved Handling Of Node String Printout 2135 Malasky Other Two CursorProcesses In Put After NewSession 2186 McJones Other Lister: Code Listings To Show Global Frame Size 2242 Johnsson Other IncludeChecker vs. Compiler switches 2253 Otto Other IncludeChecker chokes on STAR НО_─ПjНО^CПjНО]ПjНО[иПjНОZ▄ПjНОYOПjНОXПjНОVуПjНОU≤ПjНОT[ПjНОSПjНОQАПjНОPєПjНОOgПjНОN*ПjНОLМПjНОK╟ПjНОJsПjНОI6ПjНОGЫПjНОF╪ПjНОEПjНОDBПjНОCПjНОAхПjНО@▀ПjНО?NПjНО>ПjНО<тПjНО;≈ПjНО:ZПjНО9ПjНО7ЮПjНО6ёПjНО5fПjНО4)ПjНО2ЛПjНО1╞ПjНО0rПjНО/5ПjНО-ЬПjНО,╩ПjНО+~ПjНО*AПjНО)ПjНО'гПjНО&┼ПjНО%MПjНО$ПjНО"сПjНО!√ПjНО YПjНОПjНОъПjНО╒ПjНОeПjНО(ПjНОКПjНОўПjНОqПjНО4ПjНОВПjНО╨ПjНО}ПjНО@ПjНОПjНО фПjНО┴ПjНОLПjНО ПjНОрПjНО∙ПjНОXПjНОПjНОчПjНО║ПjНОdПjНО'Пj LqЖGО`ҐD2255 Karlton Other IncludeChecker should specify compilation as late as possibl 2339 Wick Other Copyright Notice on Mesa Source Files 2392 Ladner Other XFER Tool Enhancements 3303 Newman Other IncludeChecker: bug fixes 3744 Johnsson Other RunMesa 34.8 lies about widebody non XMesa machines 4166 Levin Other RunMesa: optionally restricting memory use 4647 Luniewski Other Packager: Crashes if errors while processing 4650 Luniewski Other Packager: /l produces both .list and .map files 4651 Luniewski Other Packager: Fatal error: Unbound procedure 4659 Luniewski Other Packager: /m option - More information requested 4663 Luniewski Other Packager: /m option produces fatal error 4683 Luniewski Other Packager: Missing file does not produce error message 4707 Luniewski Other Packager: multiple module instances 4737 Evans Other Formatter: Doesn't DO x_SELECT..1=>n,ENDCASE=>ERROR; 4863 Luniewski Other Packager: Can't process compiler bcd's 4865 Gobbel Other Formatter spaces too wide 4939 Levin Other CommandCentral selection glitch 5058 forrest Other Formatter adds extra blank lines 5082 BLewis Other Formatter: Improper treatment of "~=" operator 5084 BLewis Other Formatter: Improper treatment of "~(a OR b)" 5250 Gobbel Other Formatter should use small font for predeclared identifiers. 5311 Sapsford Other Formatter: Extraneous CR 5313 Mitchell Other Formatter: Use of tabs and spaces 5325 Nelson Other Formatter handles string contants wrong 5327 Morris Other Formatter problem 5344 Levin Other Formatter: comments on END procedure lines 5434 Daniels Other Statistics: InsufficientVM raised upon initialization 5480 Johnsson Other Formatter: Overlaid variant records 2007 Murray System Image Files Poisoned With Bad FP 2161 Murray System Swapper/Disk IO Difficulties 2224 Ayers System ERROR in MakeCheckPoint 3061 israel System Nil and bounds checking 3129 Olmstead System Request for info 3661 Birrell System Aborting process in ReadChar leaves keyboard monitor locked 3668 Birrell System XMesa Nucleus: determining memory size 4397 Murray System Loading garbage: Uncaught BadFile 4405 Schmidt.PA System Reading leader pages: don't change read-date 4574 Newman System RESUMEing a PointerFault=>uncaught SIGNAL InvalidGlobalFrame 4604 Newman System FrameDefs.[New/Run]Config should return a GlobalFrameHandle 4847 AWells System Bug in turning off echos in ReadLine (IODefs) 4932 Levin System Bug in AltoLoader.Load 4933 Sandman System BcdOps.ProcessSpaces lacks *SIZE[SpaceID] 4938 Levin System CommandCentral: Expand @file1 @file2 fails 4958 Levin System Bug in Wart: InitLoadState was changed 4970 Evans System Debugger looses bitmap when client makes checkpoint 4985 Newman System Loader doesn't link up imported POINTER TO FRAME 5003 Evans System MakeImage: Disk Descriptor not swapped in when needed 5057 kolling System Doc: Where is the stuff that used to be in bootdefs? 5065 McGregor System Preserving /k when coming back from a MakeCheckpoint 5094 Murray System MakeImage dies 5108 Karlton System Time: add Time.Packed to ease compatibility problems 5147 Levin System Nasty FSP bug...again! 5154 Murray System TimeConvert.PackDT off by an hour 5184 Levin System HyperRegion bug: rover not in bounds 5185 Levin System AllocVM: specific allocation too restrictive 5190 McJones System CommandCentral should parse the options window fields 5191 McJones System Uncaught signal when CommandCentral can't find compiler 5296 Hayes System Memory Competition Tajo vs. Debugger 5342 schmidt System GetID vs. GetId in CharIO.mesa 5416 Levin System Debugger smashes HyperRegion 5449 Levin System Missing Start Traps 5479 kolling System where is debugnub.bcd/mesa? 5626 Levin System LoadConfig returns ControlModule, not GlobalFrame 5627 Levin System Killing off the Interrupt process НО_─ПjНО^CПjНО]ПjНО[иПjНОZ▄ПjНОYOПjНОXПjНОVуПjНОU≤ПjНОT[ПjНОSПjНОQАПjНОPєПjНОOgПjНОN*ПjНОLМПjНОK╟ПjНОJsПjНОI6ПjНОGЫПjНОF╪ПjНОEПjНОDBПjНОCПjНОAхПjНО@▀ПjНО?NПjНО>ПjНО<тПjНО;≈ПjНО:ZПjНО9ПjНО7ЮПjНО6ёПjНО5fПjНО4)ПjНО2ЛПjНО1╞ПjНО0rПjНО/5ПjНО-ЬПjНО,╩ПjНО+~ПjНО*AПjНО)ПjНО'гПjНО&┼ПjНО%MПjНО$ПjНО"сПjНО!√ПjНО YПjНОПjНОъПjНО╒ПjНОeПjНО(ПjНОКПjНОўПjНОqПjНО4ПjНОВПjНО╨ПjНО}Пj─qЖGО`Ґ TIMESROMAN MATH TIMESROMAN HELVETICA TIMESROMAN LOGO TIMESROMAN HELVETICA HELVETICA GACHA HELVETICA TIMESROMAN TIMESROMAN HELVETICA TIMESROMAN TIMESROMAN LOGO TIMESROMAN HELVETICA TIMESROMAN HELVETICA MATH TIMESROMAN TIMESROMAN TIMESROMAN TIMESROMAN GACHA TIMESROMAN HELVETICA HELVETICA HELVETICA TIMESROMAN TIMESROMAN HELVETICA TIMESROMAN LOGO TIMESROMAN HELVETICA HELVETICA TIMESROMAN HELVETICA GACHA HELVETICA TIMESROMAN HELVETICA HELVETICA HELVETICA LOGOGACHAМ{ н-Е&v,S4 =TE{H*M RіY╒`Пg÷jЫq xzМ─А┤°┼Х▓ ╒кєyО#.■@■R╡a·#*█ "┐B" : ;Ф*╙P╙PіB!l*П":Е:ФB: ;Z":ФB":ДJ"9WФ┼"iT"=·#B ": C" 9ФB":ФqB)ЬB:Z":Ф*:НB":Е┐B"i^: #: ФB":Ф┌P┌P*▌J"┌P┌P*▌J":Е┌P┌PB"*iA":ФB: ;Z: ;Z┤j/g eЪЪ∙Ъh)ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪ Mesa60m.pressSweet29-Sep-80 8:52:09 PDTe