Intel XENIX 286 Programmers Guide (86) - Tenox.tc
Intel XENIX 286 Programmers Guide (86) - Tenox.tc Intel XENIX 286 Programmers Guide (86) - Tenox.tc
XENIX Programming SCCS: Source Code Control System Adding Comments You can add comments to an s-file by using the -y option of the delta and admin commands. This option causes the given text to be copied to the s-file as the comment for the new version. The comment may be any combination of letters, digits, and punctuation symbols. No embedded newline characters are allowed. If spaces are used, the comment must be enclosed in double quotes. The complete command must fit on one line. For example, the command delta -y"George Wheeler" s.demo.c saves the comment "George Wheeler" in the s-file s.demo.c. The -y option is typically used in shell procedures as part of an automated approach to maintaining files. When the -y option is used, the delta command does not print the corresponding comment prompt, so no interaction is required. If more than one s-file is given in the command line, the given comment applies to them all. Changing Comments You can change the comments in an s-file by using the cdc command. The command has the form cdc -rSID s. filename where -rSID gives the SID of the version with the comment to be changed, and s.filename is the name of the s-file containing the version. The command asks for a new comment by displaying the prompt comments? You may type any sequence of characters up to 512 characters long. The sequence may contain embedded newline characters if each such newline character is preceded by a backslash {\}. The sequence must be terminated with a newline character. For example, the command cdc -r3.4 s.demo.c prompts for a new comment for version 3.4. Although the command does not delete the old comment, it is no longer directly accessible by the user. The new comment contains the login name of the user who invoked the cdc command and the time the comment was changed. 5-17
SCCS: Source Code Control System XENIX Programming Adding Mod ification Requests You can add modification requests to an s-file, when the v flag is set, by using the -m option of the delta and admin commands. A modification request is a shorthand method of describing the reason for a particular version. Modification requests are usually names or numbers that the user has chosen to represent a specific request. The -m option causes the given command to save the requests following the option. A request may be any combination of letters, digits, and punctuation symbols. If spaces are used, you must enclose the request in double quotes. For example, the command delta -m" error35 optimize10" s.demo.c copies the requests "error35" and "optimizelO" to s.demo.c while saving the new version. The -m option when used with the admin command must be combined with the -i option. Furthermore, the v flag must be explicitly set with the -f option. For example, the command admin -idef.h -m" errorO" -fv s.def.h inserts the modification request "errorO" in the new file s.def.h. The delta command does not prompt for modification requests if you use the -m option. Changing Mod ification Requests You can change modification requests, when the v flag is set, by using the cdc command. The command asks for a list of modification requests by displaying the prompt MRs? You may type any number of requests. Each request may have any combination of letters, digits, or punctuation sy mbols. No more than 512 characters are allowed and the last request must be terminated with a newline character. If you wish to remove a request, you must precede the request with an exclamation mark (!). For example, the command cdc -r1.4 s.demo.c asks for changes to the modification requests. The response MRs? error36 !error3 5 adds the request "error36" and removes "error35". 5-18
- Page 31 and 32: cc: C Compiler XENIX Programming Us
- Page 33 and 34: cc: C Compiler XENIX Programming Wh
- Page 35 and 36: cc: C Compiler XENIX Programming Co
- Page 37 and 38: cc: C Compiler XENIX Programming d
- Page 39 and 40: cc: C Compiler XENIX Programming Se
- Page 41 and 42: lint: C Program Checker XENIX Progr
- Page 43 and 44: lint: C Program Checker XENIX Progr
- Page 45 and 46: lint: C Program Checker XENIX Progr
- Page 47 and 48: lint: C Program Checker XENIX Progr
- Page 49 and 50: lint: C Program Checker XENIX Progr
- Page 51 and 52: lint: C Program Checker XENIX Progr
- Page 53 and 54: make: Program Maintainer XENIX Prog
- Page 55 and 56: make: Program Maintainer XENIX Prog
- Page 57 and 58: make: Program Maintainer XENIX Prog
- Page 59 and 60: make: Program Maintainer XENIX Prog
- Page 61 and 62: make: Program Maintainer XENIX Prog
- Page 63 and 64: make: Program Maintainer XENIX Prog
- Page 65 and 66: make: Program Maintainer print: $(F
- Page 67 and 68: SCCS: Source Code Control System XE
- Page 69 and 70: SCCS: Source Code Control System XE
- Page 71 and 72: SCCS: Source Code Control System XE
- Page 73 and 74: SCCS: Source Code Control System XE
- Page 75 and 76: SCCS: Source Code Control System XE
- Page 77 and 78: SCCS: Source Code Control System XE
- Page 79 and 80: SCCS: Source Code Control System XE
- Page 81: SCCS: Source Code Control System XE
- Page 85 and 86: SCCS: Source Code Control System XE
- Page 87 and 88: SCCS: Source Code Control System XE
- Page 89 and 90: SCCS: Source Code Control System XE
- Page 91 and 92: SCCS: Source Code Control System XE
- Page 93 and 94: SCCS: Source Code Control System XE
- Page 95 and 96: SCCS: Source Code Control System XE
- Page 98 and 99: CHAPTER 6 adb: PROGRAM DEBUGGER adb
- Page 100 and 101: XENIX Programming adb: Program Debu
- Page 102 and 103: XENIX Programming adb: Program Debu
- Page 104 and 105: XENIX Programming adb: Program Debu
- Page 106 and 107: XENIX Programming adb: Program Debu
- Page 108 and 109: XENIX Programming adb: Program Debu
- Page 110 and 111: XENIX Programming adb: Program Debu
- Page 112 and 113: XENIX Programming adb: Program Debu
- Page 114 and 115: XENIX Programming adb: Program Debu
- Page 116 and 117: XENIX Programming int fcnt,gcnt,hcn
- Page 118 and 119: XENIX Programming adb: Program Debu
- Page 120 and 121: XENIX Programming adb: Program Debu
- Page 122 and 123: XENIX Programming adb: Program Debu
- Page 124 and 125: XENIX Programming adb: Program Debu
- Page 126 and 127: XENIX Programming adb: Program Debu
- Page 128: XENIX Programming adb: Program Debu
- Page 131 and 132: as: A sse m bier XENIX Programming
<strong>XENIX</strong> Programming SCCS: Source Code Control System<br />
Adding Comments<br />
You can add comments to an s-file by using the -y option of the delta and admin<br />
commands. This option causes the given text to be copied to the s-file as the comment<br />
for the new version. The comment may be any combination of letters, digits, and<br />
punctuation symbols. No embedded newline characters are allowed. If spaces are used,<br />
the comment must be enclosed in double quotes. The complete command must fit on<br />
one line. For example, the command<br />
delta -y"George Wheeler" s.demo.c<br />
saves the comment "George Wheeler" in the s-file s.demo.c.<br />
The -y option is typically used in shell procedures as part of an automated approach to<br />
maintaining files. When the -y option is used, the delta command does not print the<br />
corresponding comment prompt, so no interaction is required. If more than one s-file is<br />
given in the command line, the given comment applies to them all.<br />
Changing Comments<br />
You can change the comments in an s-file by using the cdc command. The command has<br />
the form<br />
cdc -rSID s. filename<br />
where -rSID gives the SID of the version with the comment to be changed, and<br />
s.filename is the name of the s-file containing the version. The command asks for a new<br />
comment by displaying the prompt<br />
comments?<br />
You may type any sequence of characters up to 512 characters long. The sequence may<br />
contain embedded newline characters if each such newline character is preceded by a<br />
backslash {\}. The sequence must be terminated with a newline character. For example,<br />
the command<br />
cdc -r3.4 s.demo.c<br />
prompts for a new comment for version 3.4.<br />
Although the command does not delete the old comment, it is no longer directly<br />
accessible by the user. The new comment contains the login name of the user who<br />
invoked the cdc command and the time the comment was changed.<br />
5-17