Service Manuals, User Guides, Schematic Diagrams or docs for : xerox sdd memos_1978 19781031_Minutes_October_30
<< Back | HomeMost service manuals and schematics are PDF files, so You will need Adobre Acrobat Reader to view : Acrobat Download Some of the files are DjVu format. Readers and resources available here : DjVu Resources
For the compressed files, most common are zip and rar. Please, extract files with Your favorite compression software ( WinZip, WinRAR ... ) before viewing. If a document has multiple parts, You should download all, before extracting.
Good luck. Repair on Your own risk. Make sure You know what You are doing.
Image preview - the first page of the document
>> Download 19781031_Minutes_October_30 documenatation <<
Text preview - extract from the document
Inter-Office Memorandum
To Debugger Working Group Date October 31, 1978
From Barbara Koalkin Location Palo Alto
Subject Minutes - October 30 Organization SDD/SD
litO! SDD AaCijlVES
XEROX I have read and und~ (..'
Pages_________TQ~
Filed on: [IRIS] D5 >DWG10-30.BRAVO
Reviewer Date_ _ .
I of Pages Ref .2SSPi) -~as-
Present at today's meeting: Ayers, Johnsson, Karlton, Koalkin, Satterthwaite, and Wallace.
The following is a summary of suggestions discussed at today's meeting:
* Progress has been made by Smokey and Phil towards creating a model of the
debugger/WindEx using the Tools environment. They expect to have a workable model by
mid-week so we can do some experiments.
* For the time being, type-in goes to the window containing the cursor (as in the Tools
Environment).
* We all agreed that variables should be interpreted in the stack window in the context of
whatever is "bulleted" (Le., marked). We will have to do some experiments to see whether echoing of
the input characters will be done in a subwindow of the stack window or in an interpreter window.
However, the Debug.Typescript equivalent window will be capable of doing "contextless"
interpreting (Le., arithmetic).
* To change the context: select one of the context keywordS and:
* push down the menu button. A menu of the choices will appear. Letting up the
button over one of the choices (or outside the menu to indicate no change) will make that
the context. We still need to look into how we will display a large list of information (as in 50
modules in a configuration) and indent to show the structure (for nested configurations).
* OR type in the new context terminated by CR. Smokey can provide a mechanism for this
sort of "field fill-in".
* There is no "THE current context" (as refered to in the previous memo); however, each window
has a context that is used for symbol-lookup (and marked in some way to indicate tilis).
* The initial window configuration will contain (at least): one stack window (initialized with the
information associated with the process that is currently running), one source file window, and a
debugger communication window (Le.. Debug.Answers. or a Debug.Typescript equivalent).
* We need a mechanism for telling alllhe windows (a notification) that "an bets are off' (i.e.,
a Ilew program has been loaded. some files have been deleted) so that it knows when its cache
information might be invalid.
* Smokey pointed out that the PNR nolificr mechanism of the Tools environment can
implement the same flow of control scheme as the current debugger (with respect to unwinding
the stack on proceed. procedure calls, etc.),
Minutes ◦ Jabse Service Manual Search 2024 ◦ Jabse Pravopis ◦ onTap.bg ◦ Other service manual resources online : Fixya ◦ eServiceinfo