Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Development Tools<br />
1.1<br />
5 lines<br />
Retrieves text in file "g.lang"<br />
$ get -e s.lang 1.1<br />
new delta 1.2<br />
5 lines<br />
Creates "lang" for both reading and writing, also creates ano<strong>the</strong>r file p.lang" needed by "delta". Add two<br />
more languages to <strong>the</strong> file "lang“.<br />
SNOBOL<br />
ADA<br />
Recording changes via "delta"<br />
$ delta s.lang<br />
comments ?<br />
added more languages<br />
1.2<br />
2 inserted<br />
0 deleted<br />
5 unchanged<br />
Additional info about “get”<br />
$ get -e r2 s.lang If release 2 does not exist retrieves 1.2 and names it 2.1 1.2<br />
new delta 2.1<br />
7 lines<br />
Delete COBOL from languages<br />
$ delta s.lang<br />
comments?<br />
deleted cobol from list<br />
2.1<br />
0 inserted<br />
1 deleted<br />
6 unchanged<br />
The help command<br />
$ get lang<br />
ERROR [lang]: not an SCCS file (col)<br />
$ help col<br />
col:<br />
"not an SCCS file”<br />
A file that you think is an SCCS file does not begin <strong>with</strong> <strong>the</strong> character "s"<br />
Delta Numbering<br />
Think of deltas as nodes of a tree in which <strong>the</strong> root node is <strong>the</strong> original version of <strong>the</strong> file. The root is<br />
named 1.1 and delta nodes are named 1.2, 1.3, etc. release.level.branch.sequence<br />
Debugging<br />
It usually faster and more efficient to place a few well placed print statements <strong>with</strong>in your code and recompile it,<br />
than resort to using adb/sdb. However newer debugging tools are mouse driven and extremely ease to use.<br />
ADB – absolute debugger<br />
General purpose debugger – sensitive to architecture of processor. Unless you are c assembly hacker this is a time<br />
consuming experience.<br />
adb [options] [objfile [corefile]]<br />
adb a.out core<br />
58