faq
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| faq [2010/12/27 20:19] – bil | faq [2014/04/25 17:49] (current) – wildes | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| ==== Output formatting ==== | ==== Output formatting ==== | ||
| - | See page 111 in the textbook. | + | See page 108 in the textbook. |
| ==== eCheck does not like the spacing of your output ==== | ==== eCheck does not like the spacing of your output ==== | ||
| - | Sometimes, eCheck expects a space when you have a tab (or visa versa). But eCheck communicates this using ASCII codes rather than " | + | Sometimes, eCheck expects a space when you have a tab (or visa versa). But eCheck communicates this using ASCII codes rather than " |
| ==== Reading input from a file ==== | ==== Reading input from a file ==== | ||
| - | See pages 168 and 201-202 in the textbook. | + | See pages 166 and 199-200 in the textbook. |
| ==== Object serialization (input files with .dat extension) ==== | ==== Object serialization (input files with .dat extension) ==== | ||
| - | Input files ending with .txt are text files. But (in the textbook) files ending with .dat contain a serialized object. A serialized object is an object whose state (i.e., attributes) has been written to a file. To read-in such objects, see pages 351-352 for details. | + | Input files ending with .txt are text files. But (in the textbook) files ending with .dat contain a serialized object. A serialized object is an object whose state (i.e., attributes) has been written to a file. To read-in such objects, see pages 359-360 for details. |
| ==== Interpreting compilation errors ==== | ==== Interpreting compilation errors ==== | ||
faq.1293481164.txt.gz · Last modified: 2010/12/27 20:19 by bil