diff --git a/TechDocs/Markdown/Esp/euic.md b/TechDocs/Markdown/Esp/euic.md index 4eaea51da..0971b4743 100644 --- a/TechDocs/Markdown/Esp/euic.md +++ b/TechDocs/Markdown/Esp/euic.md @@ -452,7 +452,9 @@ You can turn on or off certain bits in a record, while leaving the rest of the flags in their default settings. You do this in much the same way you do it when specifying classes, i.e. +~~~ = default + , - ... ; +~~~ **record** This is the name of the instance data field, as given in the diff --git a/TechDocs/Markdown/Tools/tini.md b/TechDocs/Markdown/Tools/tini.md index d9db0fc11..09d35d858 100644 --- a/TechDocs/Markdown/Tools/tini.md +++ b/TechDocs/Markdown/Tools/tini.md @@ -987,7 +987,7 @@ following entry: A string by which remote machines may identify you. When the remote machine sees your drives, their names will be --:. +`-:`. #### port diff --git a/TechDocs/Markdown/Tools/tswatcm.md b/TechDocs/Markdown/Tools/tswatcm.md index 3158aa53e..aed8a06e3 100644 --- a/TechDocs/Markdown/Tools/tswatcm.md +++ b/TechDocs/Markdown/Tools/tswatcm.md @@ -149,8 +149,8 @@ argument if the user gives it a particular address to look at. + `* +` An asterisk following any of the previous constructs indicates zero or more repetitions of the construct may be typed. A plus sign indicates one -or more repetitions of the construct may be used. For example, `unalias -*` can be the `unalias` command by itself, or it can be followed by +or more repetitions of the construct may be used. For example, `unalias *` +can be the `unalias` command by itself, or it can be followed by a list of words to be unaliased. ### 3.3 Address Expressions @@ -280,7 +280,7 @@ To get information about a GEOS topic, use the doc functions. apropos [] The **apropos** command searches the list of commands and command help for -all entries containing . It lists each command and its synopsis. The string may actually be a partial word. +all entries containing ``. It lists each command and its synopsis. The string may actually be a partial word. ---------- #### doc, doc-next, doc-previous @@ -626,7 +626,7 @@ This is the main command to use when setting breakpoints in C programs. The "stop in" command will set a breakpoint at the beginning of a procedure, immediately after the procedure's stack frame has been set up. The "stop at" command will set a breakpoint at the first instruction of the given source -line. If no is specified, the source file for the current stack frame is +line. If no `` is specified, the source file for the current stack frame is used. If a condition is specified by means of an "if " clause, you should enclose the expression in curly braces to prevent any nested commands, such as a "value fetch" command, from being evaluated until the breakpoint is hit. @@ -1506,7 +1506,7 @@ are being sent to the object at addr. If no argument is given, then any current **Swat Display 3-13 The objwatch Command** - mess1:0) 2 => objwatch Mess1View + (mess1:0) 2 => objwatch Mess1View brk5 (mess1:0) 3 => c MSG_META_MOUSE_PTR, ^l44a0h:0020h, GenViewClass @@ -1640,7 +1640,7 @@ the previous command. + Address History Swat has an address history which is composed of tokens for address expressions previously used by commands such as print or pobj. The -elements in the history can be accessed by typing @ where the +elements in the history can be accessed by typing `@` where the number argument is the number of the item in the history. These elements can replace a full address expression (except constants) and are often used when traversing through fields of a previously printed @@ -1729,8 +1729,8 @@ HOME environment variable patient-default mess1 run - This example shows a sample initialization file which sets up windows to display the source code - and current register values, set the length of the save buffer to 500 lines, and continue running swat - until the mess1 application has been loaded, at which point execution will automatically stop. +This example shows a sample initialization file which sets up windows to display the source code +and current register values, set the length of the save buffer to 500 lines, and continue running swat +until the mess1 application has been loaded, at which point execution will automatically stop. [System Configuration](tconfig.md) <--    [Table of Contents](../tools.md)    --> [Swat Reference](tswta_i.md) \ No newline at end of file diff --git a/TechDocs/Markdown/Tools/tswtj_z.md b/TechDocs/Markdown/Tools/tswtj_z.md index 59f605848..9bdb3edbe 100644 --- a/TechDocs/Markdown/Tools/tswtj_z.md +++ b/TechDocs/Markdown/Tools/tswtj_z.md @@ -4953,7 +4953,7 @@ returned as \n). array. Structures, unions and records are returned as a list of elements, each of -which is a 3-element list: `{ }` `` is +which is a 3-element list: `{ }`. `` is the name of the field, `` is the type token for the type of data stored in the field, and `` is the value list for the data in the field, appropriate to its data type. @@ -4962,8 +4962,7 @@ appropriate to its data type. if a structure has a field that is an array, the `` element in the list that describes that particular field will be itself a list whose elements are the elements of the array. If that array were an array of structures, each -element of that list would again be a list of `{ -}` lists. +element of that list would again be a list of `{ }` lists. + The "field" command is very useful when you want to extract the value for a structure field from a value list. @@ -5400,8 +5399,7 @@ Examine memory as a dump of words. address after the last examined memory location is used. If no address has been examined then DS:SI is used for the address. -+ The `` argument is the number of bytes to examine. It defaults to -8. ++ The `` argument is the number of bytes to examine. It defaults to 8. + Pressing `` after this command continues the list. diff --git a/TechDocs/Markdown/Tools/ttcl.md b/TechDocs/Markdown/Tools/ttcl.md index 2c7ac34c4..bf59e0033 100644 --- a/TechDocs/Markdown/Tools/ttcl.md +++ b/TechDocs/Markdown/Tools/ttcl.md @@ -1694,7 +1694,7 @@ purposes. "uplevel 1 {var foo 36}", you would modify (or create) the variable "foo" in your caller's scope. `<= 0` - Indicates the number of scopes to go down from the global one. -"uplevel 0 `` will execute in the top-most scope, +"uplevel 0 `` will execute `` in the top-most scope, which means that no local variables are involved, and any variables created by the commands in `` persist as global variables. @@ -2338,8 +2338,8 @@ element of the result with the "index" command, however; you'll have to use the "range" command to get the first 8 characters, then use "index" to trim the trailing spaces off, if you want to. -+ "patient data" returns a three-element list: `{ -}` `` and `` are the same as returned by ++ "patient data" returns a three-element list: `{ }`. +`` and `` are the same as returned by the "name" and "fullname" subcommands. ` is the number of the current thread for the patient. Each patient has a single thread that is the one the user looked at most recently, and that is its @@ -2528,8 +2528,8 @@ passed address. uniquely identifies the symbol. Thus if a procedure-local variable belongs to the current patient, the fullname would be `::::` - where `` is the segment holding the ``, which is the -procedure for which the local variable named is defined. +where `` is the segment holding the ``, which is the +procedure for which the local variable named `` is defined. + You can force the prepending of the owning patient to the fullname by passing `` as a non-empty argument ("yes" or "1" are both @@ -2930,8 +2930,8 @@ of `{ }` pairs for the members of the enumerated type. of pointer ("near", "far", "seg", "lmem", "handle", or "object") and the token for the type to which it points. -+ "type bfget" returns a three-list for the given bitfield type: `{ - }` ++ "type bfget" returns a three-list for the given bitfield type: +`{ }` + "type signed" returns non-zero if the type is signed. If the `` is not an int-class type, it is considered unsigned. @@ -2972,8 +2972,8 @@ procedure has not been loaded into Swat yet (i.e. it has not been used yet). If this is the case, Swat will have no information about the procedure and will thus print nothing. The command must be loaded into Swat either with the load command, or by just typing the command name which will usually -autoload the command. (See section 5.7.) Then the `info body -` command can be used. +autoload the command. (See section 5.7.) Then the +`info body ` command can be used. Some code examples: diff --git a/TechDocs/Markdown/Tools/ttools.md b/TechDocs/Markdown/Tools/ttools.md index 71c16fa36..b58e09847 100644 --- a/TechDocs/Markdown/Tools/ttools.md +++ b/TechDocs/Markdown/Tools/ttools.md @@ -1006,7 +1006,7 @@ sent by any program that can access the serial port. **1** - Notify PCCOM that a file is on its way. Send the Send File escape character sequence to the serial port, notifying PCCOM that a file is about to be sent to it. The escape sequence is -XF1. +`XF1`. **2** - Send the destination file name. Send the name PCCOM should use for the file when saving it. The name @@ -1111,7 +1111,7 @@ of commands is different, however, and is listed below. **1** - Notify PCCOM that you're getting a file. Send the Get File escape character sequence to the serial port, notifying PCCOM that it should get ready to send a file. The escape sequence is -XF2. +`XF2`. **2** - Send the source file name. Send the name of the file to be retrieved. The name is a string of diff --git a/Tools/swat/ibm86.c b/Tools/swat/ibm86.c index d8eb46bff..5eff68447 100644 --- a/Tools/swat/ibm86.c +++ b/Tools/swat/ibm86.c @@ -4190,7 +4190,7 @@ Ibm86DecodeInt(byte *ibuf, /* Buffer of bytes to decode */ Boolean prefixSize[2] = {FALSE, FALSE} ; byte * ibuf2; /* Start of instruction without size prefixes */ #endif - OperandSize vals[2]; /* Argument values */ + OperandSize vals[3]; /* Argument values */ GeosAddr ea; /* Effective address. */ int eaNum; /* Which arg is the effective address*/ int valNum; /* Index into vals */