Mercurial > hg > octave-lyh
annotate doc/interpreter/io.txi @ 8347:fa78cb8d8a5c
corrections for typos
Here is a patch with some corrections for typos and missing/extra
words in the manual.
changeset: 8347:34fd1d1c2294
user: Brian Gough <bjg@gnu.org>
date: Wed Nov 26 11:00:15 2008 -0500
summary: [docs] can not => cannot
| author | Brian Gough<bjg@network-theory.co.uk> |
|---|---|
| date | Thu, 27 Nov 2008 10:28:24 +0100 |
| parents | 6f2d95255911 |
| children | ee9e525744f0 |
| rev | line source |
|---|---|
| 6778 | 1 @c Copyright (C) 1996, 1997, 2007 John W. Eaton |
| 7018 | 2 @c |
| 3 @c This file is part of Octave. | |
| 4 @c | |
| 5 @c Octave is free software; you can redistribute it and/or modify it | |
| 6 @c under the terms of the GNU General Public License as published by the | |
| 7 @c Free Software Foundation; either version 3 of the License, or (at | |
| 8 @c your option) any later version. | |
| 9 @c | |
| 10 @c Octave is distributed in the hope that it will be useful, but WITHOUT | |
| 11 @c ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or | |
| 12 @c FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License | |
| 13 @c for more details. | |
| 14 @c | |
| 15 @c You should have received a copy of the GNU General Public License | |
| 16 @c along with Octave; see the file COPYING. If not, see | |
| 17 @c <http://www.gnu.org/licenses/>. | |
| 3294 | 18 |
| 4169 | 19 @node Input and Output |
| 3294 | 20 @chapter Input and Output |
| 21 | |
| 6666 | 22 Octave supports several ways of reading and writing data to or from the |
| 23 prompt or a file. The most simple functions for data Input and Output | |
|
8347
fa78cb8d8a5c
corrections for typos
Brian Gough<bjg@network-theory.co.uk>
parents:
8286
diff
changeset
|
24 (I/O) are easy to use, but only provides limited control of how |
| 6666 | 25 data is processed. For more control, a set of functions modelled |
| 26 after the C standard library are also provided by Octave. | |
| 27 | |
| 28 @menu | |
| 29 * Basic Input and Output:: | |
| 30 * C-Style I/O Functions:: | |
| 31 @end menu | |
| 32 | |
| 33 @node Basic Input and Output | |
| 34 @section Basic Input and Output | |
| 35 | |
| 36 @c We could use a two-line introduction here... | |
| 37 | |
| 38 @menu | |
| 39 * Terminal Output:: | |
| 40 * Terminal Input:: | |
| 41 * Simple File I/O:: | |
| 6788 | 42 * Rational Approximations:: |
| 6666 | 43 @end menu |
| 44 | |
| 45 @node Terminal Output | |
| 46 @subsection Terminal Output | |
| 47 | |
| 48 Since Octave normally prints the value of an expression as soon as it | |
| 49 has been evaluated, the simplest of all I/O functions is a simple | |
| 50 expression. For example, the following expression will display the | |
| 51 value of @samp{pi} | |
| 52 | |
| 53 @example | |
| 54 pi | |
| 55 @print{} pi = 3.1416 | |
| 56 @end example | |
| 57 | |
| 58 This works well as long as it is acceptable to have the name of the | |
| 59 variable (or @samp{ans}) printed along with the value. To print the | |
| 60 value of a variable without printing its name, use the function | |
| 61 @code{disp}. | |
| 62 | |
| 63 The @code{format} command offers some control over the way Octave prints | |
| 64 values with @code{disp} and through the normal echoing mechanism. | |
| 65 | |
| 66 @DOCSTRING(ans) | |
| 67 | |
| 68 @DOCSTRING(disp) | |
| 69 | |
| 70 @DOCSTRING(format) | |
| 71 | |
| 72 @menu | |
| 73 * Paging Screen Output:: | |
| 74 @end menu | |
| 75 | |
| 76 @node Paging Screen Output | |
| 77 @subsubsection Paging Screen Output | |
| 78 | |
| 3294 | 79 When running interactively, Octave normally sends any output intended |
| 80 for your terminal that is more than one screen long to a paging program, | |
| 81 such as @code{less} or @code{more}. This avoids the problem of having a | |
| 82 large volume of output stream by before you can read it. With | |
| 83 @code{less} (and some versions of @code{more}) you can also scan forward | |
| 84 and backward, and search for specific items. | |
| 85 | |
| 86 Normally, no output is displayed by the pager until just before Octave | |
| 87 is ready to print the top level prompt, or read from the standard input | |
| 88 (for example, by using the @code{fscanf} or @code{scanf} functions). | |
| 89 This means that there may be some delay before any output appears on | |
| 90 your screen if you have asked Octave to perform a significant amount of | |
| 91 work with a single command statement. The function @code{fflush} may be | |
| 92 used to force output to be sent to the pager (or any other stream) | |
| 93 immediately. | |
| 94 | |
| 6666 | 95 You can select the program to run as the pager using the @code{PAGER} |
| 96 function, and you can turn paging off by using the function | |
| 97 @code{more}. | |
| 3294 | 98 |
| 3372 | 99 @DOCSTRING(more) |
| 3294 | 100 |
| 3372 | 101 @DOCSTRING(PAGER) |
| 3294 | 102 |
| 6549 | 103 @DOCSTRING(PAGER_FLAGS) |
| 104 | |
| 3372 | 105 @DOCSTRING(page_screen_output) |
| 3294 | 106 |
| 3372 | 107 @DOCSTRING(page_output_immediately) |
| 3294 | 108 |
| 3372 | 109 @DOCSTRING(fflush) |
| 3294 | 110 |
| 5775 | 111 @c FIXME -- maybe this would be a good place to describe the |
| 3294 | 112 @c following message: |
| 113 @c | |
| 114 @c warning: connection to external pager (pid = 9334) lost -- | |
| 115 @c warning: pending computations and output may be lost | |
| 116 @c warning: broken pipe | |
| 117 | |
| 4167 | 118 @node Terminal Input |
| 3294 | 119 @subsection Terminal Input |
| 120 | |
| 121 Octave has three functions that make it easy to prompt users for | |
| 122 input. The @code{input} and @code{menu} functions are normally | |
| 123 used for managing an interactive dialog with a user, and the | |
| 124 @code{keyboard} function is normally used for doing simple debugging. | |
| 125 | |
| 3372 | 126 @DOCSTRING(input) |
| 3294 | 127 |
| 3372 | 128 @DOCSTRING(menu) |
| 3294 | 129 |
| 6646 | 130 For @code{input}, the normal command line history and editing functions |
| 131 are available at the prompt. | |
| 3294 | 132 |
| 133 Octave also has a function that makes it possible to get a single | |
| 134 character from the keyboard without requiring the user to type a | |
| 135 carriage return. | |
| 136 | |
| 3372 | 137 @DOCSTRING(kbhit) |
| 3294 | 138 |
| 4167 | 139 @node Simple File I/O |
| 3294 | 140 @subsection Simple File I/O |
| 141 | |
| 5225 | 142 @cindex saving data |
| 143 @cindex loading data | |
| 3294 | 144 The @code{save} and @code{load} commands allow data to be written to and |
| 145 read from disk files in various formats. The default format of files | |
| 6666 | 146 written by the @code{save} command can be controlled using the functions |
| 147 @code{default_save_options} and @code{save_precision}. | |
| 148 | |
| 149 As an example the following code creates a 3-by-3 matrix and saves it | |
| 150 to the file @samp{myfile.mat}. | |
| 151 | |
| 152 @example | |
| 153 A = [ 1:3; 4:6; 7:9 ]; | |
| 154 save myfile.mat A | |
| 155 @end example | |
| 3294 | 156 |
| 6666 | 157 Once one or more variables have been saved to a file, they can be |
| 158 read into memory using the @code{load} command. | |
| 159 | |
| 160 @example | |
| 161 load myfile.mat | |
| 162 A | |
| 163 @print{} A = | |
| 164 @print{} | |
| 165 @print{} 1 2 3 | |
| 166 @print{} 4 5 6 | |
| 167 @print{} 7 8 9 | |
| 168 @end example | |
| 3294 | 169 |
| 3372 | 170 @DOCSTRING(save) |
| 3294 | 171 |
| 6666 | 172 @DOCSTRING(load) |
| 173 | |
| 174 There are three functions that modify the behavior of @code{save}. | |
| 175 | |
| 176 @DOCSTRING(default_save_options) | |
| 177 | |
| 178 @DOCSTRING(save_precision) | |
| 179 | |
| 180 @DOCSTRING(save_header_format_string) | |
| 181 | |
| 182 @DOCSTRING(native_float_format) | |
| 183 | |
| 184 It is possible to write data to a file in a way much similar to the | |
| 185 @code{disp} function for writing data to the screen. The @code{fdisp} | |
| 186 works just like @code{disp} except its first argument is a file pointer | |
| 187 as created by @code{fopen}. As an example, the following code writes | |
| 188 to data @samp{myfile.txt}. | |
| 189 | |
| 190 @example | |
| 191 fid = fopen ("myfile.txt", "w"); | |
| 192 fdisp (fid, "3/8 is "); | |
| 193 fdisp (fid, 3/8); | |
| 194 fclose (fid); | |
| 195 @end example | |
| 196 | |
| 197 @noindent | |
| 198 @xref{Opening and Closing Files}, for details on how to use @code{fopen} | |
| 199 and @code{fclose}. | |
| 200 | |
| 201 @DOCSTRING(fdisp) | |
| 202 | |
|
7580
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
203 Octave can also read and write matrices text files such as comma |
|
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
204 separated lists. |
|
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
205 |
|
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
206 @DOCSTRING(dlmwrite) |
|
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
207 |
|
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
208 @DOCSTRING(dlmread) |
|
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
209 |
|
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
210 @DOCSTRING(csvwrite) |
|
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
211 |
|
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
212 @DOCSTRING(csvread) |
|
b4aa9ef3d3ef
Port dlmread, dlmwrite, csvread and csvwrite from octave-forge
David Bateman <dbateman@free.fr>
parents:
7336
diff
changeset
|
213 |
| 6666 | 214 @menu |
| 215 * Saving Data on Unexpected Exits:: | |
| 216 @end menu | |
| 217 | |
| 218 @node Saving Data on Unexpected Exits | |
| 219 @subsubsection Saving Data on Unexpected Exits | |
| 220 | |
|
8347
fa78cb8d8a5c
corrections for typos
Brian Gough<bjg@network-theory.co.uk>
parents:
8286
diff
changeset
|
221 If Octave for some reason exits unexpectedly it will by default save the |
| 6666 | 222 variables available in the workspace to a file in the current directory. |
| 223 By default this file is named @samp{octave-core} and can be loaded | |
| 224 into memory with the @code{load} command. While the default behaviour | |
| 225 most often is reasonable it can be changed through the following | |
| 226 functions. | |
| 3294 | 227 |
| 3372 | 228 @DOCSTRING(crash_dumps_octave_core) |
| 3294 | 229 |
| 4449 | 230 @DOCSTRING(sighup_dumps_octave_core) |
| 231 | |
| 232 @DOCSTRING(sigterm_dumps_octave_core) | |
| 233 | |
| 5287 | 234 @DOCSTRING(octave_core_file_options) |
| 3294 | 235 |
| 6550 | 236 @DOCSTRING(octave_core_file_limit) |
| 237 | |
| 238 @DOCSTRING(octave_core_file_name) | |
| 239 | |
| 6788 | 240 @node Rational Approximations |
| 241 @subsection Rational Approximations | |
| 242 | |
| 243 @DOCSTRING(rat) | |
| 244 | |
| 245 @DOCSTRING(rats) | |
| 6550 | 246 |
| 4167 | 247 @node C-Style I/O Functions |
| 3294 | 248 @section C-Style I/O Functions |
| 249 | |
| 250 Octave's C-style input and output functions provide most of the | |
| 251 functionality of the C programming language's standard I/O library. The | |
| 252 argument lists for some of the input functions are slightly different, | |
| 253 however, because Octave has no way of passing arguments by reference. | |
| 254 | |
| 255 In the following, @var{file} refers to a file name and @code{fid} refers | |
| 256 to an integer file number, as returned by @code{fopen}. | |
| 257 | |
| 258 There are three files that are always available. Although these files | |
| 259 can be accessed using their corresponding numeric file ids, you should | |
| 260 always use the symbolic names given in the table below, since it will | |
| 261 make your programs easier to understand. | |
| 262 | |
| 3372 | 263 @DOCSTRING(stdin) |
| 3294 | 264 |
| 3372 | 265 @DOCSTRING(stdout) |
| 3294 | 266 |
| 3372 | 267 @DOCSTRING(stderr) |
| 3294 | 268 |
| 269 @menu | |
| 270 * Opening and Closing Files:: | |
| 271 * Simple Output:: | |
| 272 * Line-Oriented Input:: | |
| 273 * Formatted Output:: | |
| 274 * Output Conversion for Matrices:: | |
| 275 * Output Conversion Syntax:: | |
| 276 * Table of Output Conversions:: | |
| 277 * Integer Conversions:: | |
| 278 * Floating-Point Conversions:: Other Output Conversions:: | |
| 279 * Other Output Conversions:: | |
| 280 * Formatted Input:: | |
| 281 * Input Conversion Syntax:: | |
| 282 * Table of Input Conversions:: | |
| 283 * Numeric Input Conversions:: | |
| 284 * String Input Conversions:: | |
| 285 * Binary I/O:: | |
| 286 * Temporary Files:: | |
| 287 * EOF and Errors:: | |
| 288 * File Positioning:: | |
| 289 @end menu | |
| 290 | |
| 4167 | 291 @node Opening and Closing Files |
| 3294 | 292 @subsection Opening and Closing Files |
| 293 | |
| 6666 | 294 When reading data from a file it must be opened for reading first, and |
| 295 likewise when writing to a file. The @code{fopen} function returns a | |
| 296 pointer to an open file that is ready to be read or written. Once all | |
| 297 data has been read from or written to the opened file it should be closed. | |
| 298 The @code{fclose} function does this. The following code illustrates | |
| 299 the basic pattern for writing to a file, but a very similar pattern is | |
| 300 used when reading a file. | |
| 301 | |
| 302 @example | |
| 303 filename = "myfile.txt"; | |
| 304 fid = fopen (filename, "w"); | |
| 305 # Do the actual I/O here... | |
| 306 fclose (fid); | |
| 307 @end example | |
| 308 | |
| 3372 | 309 @DOCSTRING(fopen) |
| 3294 | 310 |
| 3372 | 311 @DOCSTRING(fclose) |
| 3294 | 312 |
| 4167 | 313 @node Simple Output |
| 3294 | 314 @subsection Simple Output |
| 315 | |
| 6666 | 316 Once a file has been opened for writing a string can be written to the |
| 317 file using the @code{fputs} function. The following example shows | |
| 318 how to write the string @samp{Free Software is needed for Free Science} | |
| 319 to the file @samp{free.txt}. | |
| 320 | |
| 321 @example | |
| 322 filename = "free.txt"; | |
| 323 fid = fopen (filename, "w"); | |
| 324 fputs (fid, "Free Software is needed for Free Science"); | |
| 325 fclose (fid); | |
| 326 @end example | |
| 327 | |
| 3372 | 328 @DOCSTRING(fputs) |
| 3294 | 329 |
| 6666 | 330 A function much similar to @code{fputs} is available for writing data |
| 331 to the screen. The @code{puts} function works just like @code{fputs} | |
| 332 except it doesn't take a file pointer as its input. | |
| 333 | |
| 3372 | 334 @DOCSTRING(puts) |
| 3294 | 335 |
| 4167 | 336 @node Line-Oriented Input |
| 3294 | 337 @subsection Line-Oriented Input |
| 338 | |
| 6666 | 339 To read from a file it must be opened for reading using @code{fopen}. |
| 340 Then a line can be read from the file using @code{fgetl} as the following | |
| 341 code illustrates | |
| 342 | |
| 343 @example | |
| 344 fid = fopen ("free.txt"); | |
| 345 txt = fgetl (fid) | |
| 346 @print{} Free Software is needed for Free Science | |
| 347 fclose (fid); | |
| 348 @end example | |
| 349 | |
| 350 @noindent | |
| 351 This of course assumes that the file @samp{free.txt} exists and contains | |
| 352 the line @samp{Free Software is needed for Free Science}. | |
| 353 | |
| 3372 | 354 @DOCSTRING(fgetl) |
| 3294 | 355 |
| 3372 | 356 @DOCSTRING(fgets) |
| 3294 | 357 |
| 4167 | 358 @node Formatted Output |
| 3294 | 359 @subsection Formatted Output |
| 360 | |
| 361 This section describes how to call @code{printf} and related functions. | |
| 362 | |
| 363 The following functions are available for formatted output. They are | |
| 364 modelled after the C language functions of the same name, but they | |
| 365 interpret the format template differently in order to improve the | |
| 366 performance of printing vector and matrix values. | |
| 367 | |
| 3372 | 368 @DOCSTRING(printf) |
| 3294 | 369 |
| 3372 | 370 @DOCSTRING(fprintf) |
| 3294 | 371 |
| 3372 | 372 @DOCSTRING(sprintf) |
| 3294 | 373 |
| 374 The @code{printf} function can be used to print any number of arguments. | |
| 375 The template string argument you supply in a call provides | |
| 376 information not only about the number of additional arguments, but also | |
| 377 about their types and what style should be used for printing them. | |
| 378 | |
| 379 Ordinary characters in the template string are simply written to the | |
| 380 output stream as-is, while @dfn{conversion specifications} introduced by | |
| 381 a @samp{%} character in the template cause subsequent arguments to be | |
| 382 formatted and written to the output stream. For example, | |
| 383 @cindex conversion specifications (@code{printf}) | |
| 384 | |
| 6670 | 385 @example |
| 3294 | 386 pct = 37; |
| 387 filename = "foo.txt"; | |
| 7031 | 388 printf ("Processed %d%% of `%s'.\nPlease be patient.\n", |
| 389 pct, filename); | |
| 6670 | 390 @end example |
| 3294 | 391 |
| 392 @noindent | |
| 393 produces output like | |
| 394 | |
| 6670 | 395 @example |
| 7031 | 396 Processed 37% of `foo.txt'. |
| 3294 | 397 Please be patient. |
| 6670 | 398 @end example |
| 3294 | 399 |
| 400 This example shows the use of the @samp{%d} conversion to specify that a | |
| 401 scalar argument should be printed in decimal notation, the @samp{%s} | |
| 402 conversion to specify printing of a string argument, and the @samp{%%} | |
| 403 conversion to print a literal @samp{%} character. | |
| 404 | |
| 405 There are also conversions for printing an integer argument as an | |
| 406 unsigned value in octal, decimal, or hexadecimal radix (@samp{%o}, | |
| 407 @samp{%u}, or @samp{%x}, respectively); or as a character value | |
| 408 (@samp{%c}). | |
| 409 | |
| 410 Floating-point numbers can be printed in normal, fixed-point notation | |
| 411 using the @samp{%f} conversion or in exponential notation using the | |
| 412 @samp{%e} conversion. The @samp{%g} conversion uses either @samp{%e} | |
| 413 or @samp{%f} format, depending on what is more appropriate for the | |
| 414 magnitude of the particular number. | |
| 415 | |
| 416 You can control formatting more precisely by writing @dfn{modifiers} | |
| 417 between the @samp{%} and the character that indicates which conversion | |
| 418 to apply. These slightly alter the ordinary behavior of the conversion. | |
| 419 For example, most conversion specifications permit you to specify a | |
| 420 minimum field width and a flag indicating whether you want the result | |
| 421 left- or right-justified within the field. | |
| 422 | |
| 423 The specific flags and modifiers that are permitted and their | |
| 424 interpretation vary depending on the particular conversion. They're all | |
| 425 described in more detail in the following sections. | |
| 426 | |
| 4167 | 427 @node Output Conversion for Matrices |
| 3294 | 428 @subsection Output Conversion for Matrices |
| 429 | |
| 430 When given a matrix value, Octave's formatted output functions cycle | |
| 431 through the format template until all the values in the matrix have been | |
| 432 printed. For example, | |
| 433 | |
| 434 @example | |
| 435 @group | |
| 436 printf ("%4.2f %10.2e %8.4g\n", hilb (3)); | |
| 437 | |
| 438 @print{} 1.00 5.00e-01 0.3333 | |
| 439 @print{} 0.50 3.33e-01 0.25 | |
| 440 @print{} 0.33 2.50e-01 0.2 | |
| 441 @end group | |
| 442 @end example | |
| 443 | |
| 444 If more than one value is to be printed in a single call, the output | |
| 445 functions do not return to the beginning of the format template when | |
| 446 moving on from one value to the next. This can lead to confusing output | |
| 447 if the number of elements in the matrices are not exact multiples of the | |
| 448 number of conversions in the format template. For example, | |
| 449 | |
| 450 @example | |
| 451 @group | |
| 452 printf ("%4.2f %10.2e %8.4g\n", [1, 2], [3, 4]); | |
| 453 | |
| 454 @print{} 1.00 2.00e+00 3 | |
| 455 @print{} 4.00 | |
| 456 @end group | |
| 457 @end example | |
| 458 | |
| 459 If this is not what you want, use a series of calls instead of just one. | |
| 460 | |
| 4167 | 461 @node Output Conversion Syntax |
| 3294 | 462 @subsection Output Conversion Syntax |
| 463 | |
| 464 This section provides details about the precise syntax of conversion | |
| 465 specifications that can appear in a @code{printf} template | |
| 466 string. | |
| 467 | |
| 468 Characters in the template string that are not part of a | |
| 469 conversion specification are printed as-is to the output stream. | |
| 470 | |
| 471 The conversion specifications in a @code{printf} template string have | |
| 472 the general form: | |
| 473 | |
| 6670 | 474 @example |
| 3294 | 475 % @var{flags} @var{width} @r{[} . @var{precision} @r{]} @var{type} @var{conversion} |
| 6670 | 476 @end example |
| 3294 | 477 |
| 478 For example, in the conversion specifier @samp{%-10.8ld}, the @samp{-} | |
| 479 is a flag, @samp{10} specifies the field width, the precision is | |
| 480 @samp{8}, the letter @samp{l} is a type modifier, and @samp{d} specifies | |
| 481 the conversion style. (This particular type specifier says to print a | |
| 482 numeric argument in decimal notation, with a minimum of 8 digits | |
| 483 left-justified in a field at least 10 characters wide.) | |
| 484 | |
| 485 In more detail, output conversion specifications consist of an | |
| 486 initial @samp{%} character followed in sequence by: | |
| 487 | |
| 488 @itemize @bullet | |
| 489 @item | |
| 490 Zero or more @dfn{flag characters} that modify the normal behavior of | |
| 491 the conversion specification. | |
| 492 @cindex flag character (@code{printf}) | |
| 493 | |
| 494 @item | |
| 495 An optional decimal integer specifying the @dfn{minimum field width}. | |
| 496 If the normal conversion produces fewer characters than this, the field | |
| 497 is padded with spaces to the specified width. This is a @emph{minimum} | |
| 498 value; if the normal conversion produces more characters than this, the | |
| 499 field is @emph{not} truncated. Normally, the output is right-justified | |
| 500 within the field. | |
| 501 @cindex minimum field width (@code{printf}) | |
| 502 | |
| 503 You can also specify a field width of @samp{*}. This means that the | |
| 504 next argument in the argument list (before the actual value to be | |
| 505 printed) is used as the field width. The value is rounded to the | |
| 506 nearest integer. If the value is negative, this means to set the | |
| 507 @samp{-} flag (see below) and to use the absolute value as the field | |
| 508 width. | |
| 509 | |
| 510 @item | |
| 511 An optional @dfn{precision} to specify the number of digits to be | |
| 512 written for the numeric conversions. If the precision is specified, it | |
| 513 consists of a period (@samp{.}) followed optionally by a decimal integer | |
| 514 (which defaults to zero if omitted). | |
| 515 @cindex precision (@code{printf}) | |
| 516 | |
| 517 You can also specify a precision of @samp{*}. This means that the next | |
| 518 argument in the argument list (before the actual value to be printed) is | |
| 519 used as the precision. The value must be an integer, and is ignored | |
| 520 if it is negative. | |
| 521 | |
| 522 @item | |
| 523 An optional @dfn{type modifier character}. This character is ignored by | |
| 524 Octave's @code{printf} function, but is recognized to provide | |
| 525 compatibility with the C language @code{printf}. | |
| 526 | |
| 527 @item | |
| 528 A character that specifies the conversion to be applied. | |
| 529 @end itemize | |
| 530 | |
| 531 The exact options that are permitted and how they are interpreted vary | |
| 532 between the different conversion specifiers. See the descriptions of the | |
| 533 individual conversions for information about the particular options that | |
| 534 they use. | |
| 535 | |
| 4167 | 536 @node Table of Output Conversions |
| 3294 | 537 @subsection Table of Output Conversions |
| 538 @cindex output conversions, for @code{printf} | |
| 539 | |
| 540 Here is a table summarizing what all the different conversions do: | |
| 541 | |
| 542 @table @asis | |
| 543 @item @samp{%d}, @samp{%i} | |
| 544 Print an integer as a signed decimal number. @xref{Integer | |
| 545 Conversions}, for details. @samp{%d} and @samp{%i} are synonymous for | |
| 546 output, but are different when used with @code{scanf} for input | |
| 547 (@pxref{Table of Input Conversions}). | |
| 548 | |
| 549 @item @samp{%o} | |
| 550 Print an integer as an unsigned octal number. @xref{Integer | |
| 551 Conversions}, for details. | |
| 552 | |
| 553 @item @samp{%u} | |
| 554 Print an integer as an unsigned decimal number. @xref{Integer | |
| 555 Conversions}, for details. | |
| 556 | |
| 557 @item @samp{%x}, @samp{%X} | |
| 558 Print an integer as an unsigned hexadecimal number. @samp{%x} uses | |
| 559 lower-case letters and @samp{%X} uses upper-case. @xref{Integer | |
| 560 Conversions}, for details. | |
| 561 | |
| 562 @item @samp{%f} | |
| 563 Print a floating-point number in normal (fixed-point) notation. | |
| 564 @xref{Floating-Point Conversions}, for details. | |
| 565 | |
| 566 @item @samp{%e}, @samp{%E} | |
| 567 Print a floating-point number in exponential notation. @samp{%e} uses | |
| 568 lower-case letters and @samp{%E} uses upper-case. @xref{Floating-Point | |
| 569 Conversions}, for details. | |
| 570 | |
| 571 @item @samp{%g}, @samp{%G} | |
| 572 Print a floating-point number in either normal (fixed-point) or | |
| 573 exponential notation, whichever is more appropriate for its magnitude. | |
| 574 @samp{%g} uses lower-case letters and @samp{%G} uses upper-case. | |
| 575 @xref{Floating-Point Conversions}, for details. | |
| 576 | |
| 577 @item @samp{%c} | |
| 578 Print a single character. @xref{Other Output Conversions}. | |
| 579 | |
| 580 @item @samp{%s} | |
| 581 Print a string. @xref{Other Output Conversions}. | |
| 582 | |
| 583 @item @samp{%%} | |
| 584 Print a literal @samp{%} character. @xref{Other Output Conversions}. | |
| 585 @end table | |
| 586 | |
| 587 If the syntax of a conversion specification is invalid, unpredictable | |
| 588 things will happen, so don't do this. If there aren't enough function | |
| 589 arguments provided to supply values for all the conversion | |
| 590 specifications in the template string, or if the arguments are not of | |
| 591 the correct types, the results are unpredictable. If you supply more | |
| 592 arguments than conversion specifications, the extra argument values are | |
| 593 simply ignored; this is sometimes useful. | |
| 594 | |
| 4167 | 595 @node Integer Conversions |
| 3294 | 596 @subsection Integer Conversions |
| 597 | |
| 598 This section describes the options for the @samp{%d}, @samp{%i}, | |
| 599 @samp{%o}, @samp{%u}, @samp{%x}, and @samp{%X} conversion | |
| 600 specifications. These conversions print integers in various formats. | |
| 601 | |
| 602 The @samp{%d} and @samp{%i} conversion specifications both print an | |
| 603 numeric argument as a signed decimal number; while @samp{%o}, | |
| 604 @samp{%u}, and @samp{%x} print the argument as an unsigned octal, | |
| 605 decimal, or hexadecimal number (respectively). The @samp{%X} conversion | |
| 606 specification is just like @samp{%x} except that it uses the characters | |
| 607 @samp{ABCDEF} as digits instead of @samp{abcdef}. | |
| 608 | |
| 609 The following flags are meaningful: | |
| 610 | |
| 611 @table @asis | |
| 612 @item @samp{-} | |
| 613 Left-justify the result in the field (instead of the normal | |
| 614 right-justification). | |
| 615 | |
| 616 @item @samp{+} | |
| 617 For the signed @samp{%d} and @samp{%i} conversions, print a | |
| 618 plus sign if the value is positive. | |
| 619 | |
| 620 @item @samp{ } | |
| 621 For the signed @samp{%d} and @samp{%i} conversions, if the result | |
| 622 doesn't start with a plus or minus sign, prefix it with a space | |
| 623 character instead. Since the @samp{+} flag ensures that the result | |
| 624 includes a sign, this flag is ignored if you supply both of them. | |
| 625 | |
| 626 @item @samp{#} | |
| 627 For the @samp{%o} conversion, this forces the leading digit to be | |
| 628 @samp{0}, as if by increasing the precision. For @samp{%x} or | |
| 629 @samp{%X}, this prefixes a leading @samp{0x} or @samp{0X} (respectively) | |
| 630 to the result. This doesn't do anything useful for the @samp{%d}, | |
| 631 @samp{%i}, or @samp{%u} conversions. | |
| 632 | |
| 633 @item @samp{0} | |
| 634 Pad the field with zeros instead of spaces. The zeros are placed after | |
| 635 any indication of sign or base. This flag is ignored if the @samp{-} | |
| 636 flag is also specified, or if a precision is specified. | |
| 637 @end table | |
| 638 | |
| 639 If a precision is supplied, it specifies the minimum number of digits to | |
| 640 appear; leading zeros are produced if necessary. If you don't specify a | |
| 641 precision, the number is printed with as many digits as it needs. If | |
| 642 you convert a value of zero with an explicit precision of zero, then no | |
| 643 characters at all are produced. | |
| 644 | |
| 4167 | 645 @node Floating-Point Conversions |
| 3294 | 646 @subsection Floating-Point Conversions |
| 647 | |
| 648 This section discusses the conversion specifications for floating-point | |
| 649 numbers: the @samp{%f}, @samp{%e}, @samp{%E}, @samp{%g}, and @samp{%G} | |
| 650 conversions. | |
| 651 | |
| 652 The @samp{%f} conversion prints its argument in fixed-point notation, | |
| 653 producing output of the form | |
| 654 @w{[@code{-}]@var{ddd}@code{.}@var{ddd}}, | |
| 655 where the number of digits following the decimal point is controlled | |
| 656 by the precision you specify. | |
| 657 | |
| 658 The @samp{%e} conversion prints its argument in exponential notation, | |
| 659 producing output of the form | |
| 660 @w{[@code{-}]@var{d}@code{.}@var{ddd}@code{e}[@code{+}|@code{-}]@var{dd}}. | |
| 661 Again, the number of digits following the decimal point is controlled by | |
| 662 the precision. The exponent always contains at least two digits. The | |
| 663 @samp{%E} conversion is similar but the exponent is marked with the letter | |
| 664 @samp{E} instead of @samp{e}. | |
| 665 | |
| 666 The @samp{%g} and @samp{%G} conversions print the argument in the style | |
| 667 of @samp{%e} or @samp{%E} (respectively) if the exponent would be less | |
| 668 than -4 or greater than or equal to the precision; otherwise they use the | |
| 669 @samp{%f} style. Trailing zeros are removed from the fractional portion | |
| 670 of the result and a decimal-point character appears only if it is | |
| 671 followed by a digit. | |
| 672 | |
| 673 The following flags can be used to modify the behavior: | |
| 674 | |
| 675 @c Not @samp so we can have ` ' as an item. | |
| 676 @table @asis | |
| 677 @item @samp{-} | |
| 678 Left-justify the result in the field. Normally the result is | |
| 679 right-justified. | |
| 680 | |
| 681 @item @samp{+} | |
| 682 Always include a plus or minus sign in the result. | |
| 683 | |
| 684 @item @samp{ } | |
| 685 If the result doesn't start with a plus or minus sign, prefix it with a | |
| 686 space instead. Since the @samp{+} flag ensures that the result includes | |
| 687 a sign, this flag is ignored if you supply both of them. | |
| 688 | |
| 689 @item @samp{#} | |
| 690 Specifies that the result should always include a decimal point, even | |
| 691 if no digits follow it. For the @samp{%g} and @samp{%G} conversions, | |
| 692 this also forces trailing zeros after the decimal point to be left | |
| 693 in place where they would otherwise be removed. | |
| 694 | |
| 695 @item @samp{0} | |
| 696 Pad the field with zeros instead of spaces; the zeros are placed | |
| 697 after any sign. This flag is ignored if the @samp{-} flag is also | |
| 698 specified. | |
| 699 @end table | |
| 700 | |
| 701 The precision specifies how many digits follow the decimal-point | |
| 702 character for the @samp{%f}, @samp{%e}, and @samp{%E} conversions. For | |
| 703 these conversions, the default precision is @code{6}. If the precision | |
| 704 is explicitly @code{0}, this suppresses the decimal point character | |
| 705 entirely. For the @samp{%g} and @samp{%G} conversions, the precision | |
| 706 specifies how many significant digits to print. Significant digits are | |
| 707 the first digit before the decimal point, and all the digits after it. | |
| 708 If the precision is @code{0} or not specified for @samp{%g} or | |
| 709 @samp{%G}, it is treated like a value of @code{1}. If the value being | |
| 710 printed cannot be expressed precisely in the specified number of digits, | |
| 711 the value is rounded to the nearest number that fits. | |
| 712 | |
| 4167 | 713 @node Other Output Conversions |
| 3294 | 714 @subsection Other Output Conversions |
| 715 | |
| 716 This section describes miscellaneous conversions for @code{printf}. | |
| 717 | |
| 718 The @samp{%c} conversion prints a single character. The @samp{-} | |
| 719 flag can be used to specify left-justification in the field, but no | |
| 720 other flags are defined, and no precision or type modifier can be given. | |
| 721 For example: | |
| 722 | |
| 6670 | 723 @example |
| 3294 | 724 printf ("%c%c%c%c%c", "h", "e", "l", "l", "o"); |
| 6670 | 725 @end example |
| 3294 | 726 |
| 727 @noindent | |
| 728 prints @samp{hello}. | |
| 729 | |
| 730 The @samp{%s} conversion prints a string. The corresponding argument | |
| 731 must be a string. A precision can be specified to indicate the maximum | |
| 732 number of characters to write; otherwise characters in the string up to | |
| 733 but not including the terminating null character are written to the | |
| 734 output stream. The @samp{-} flag can be used to specify | |
| 735 left-justification in the field, but no other flags or type modifiers | |
| 736 are defined for this conversion. For example: | |
| 737 | |
| 6670 | 738 @example |
| 3294 | 739 printf ("%3s%-6s", "no", "where"); |
| 6670 | 740 @end example |
| 3294 | 741 |
| 742 @noindent | |
| 743 prints @samp{ nowhere } (note the leading and trailing spaces). | |
| 744 | |
| 4167 | 745 @node Formatted Input |
| 3294 | 746 @subsection Formatted Input |
| 747 | |
| 748 Octave provides the @code{scanf}, @code{fscanf}, and @code{sscanf} | |
| 749 functions to read formatted input. There are two forms of each of these | |
| 750 functions. One can be used to extract vectors of data from a file, and | |
| 751 the other is more `C-like'. | |
| 752 | |
| 3428 | 753 @DOCSTRING(fscanf) |
| 3294 | 754 |
|
8286
6f2d95255911
fix @seealso references to point to existing anchors
Thorsten Meyer <thorsten.meyier@gmx.de>
parents:
7580
diff
changeset
|
755 @DOCSTRING(scanf) |
|
6f2d95255911
fix @seealso references to point to existing anchors
Thorsten Meyer <thorsten.meyier@gmx.de>
parents:
7580
diff
changeset
|
756 |
| 3372 | 757 @DOCSTRING(sscanf) |
| 3294 | 758 |
| 759 Calls to @code{scanf} are superficially similar to calls to | |
| 760 @code{printf} in that arbitrary arguments are read under the control of | |
| 761 a template string. While the syntax of the conversion specifications in | |
| 762 the template is very similar to that for @code{printf}, the | |
| 763 interpretation of the template is oriented more towards free-format | |
| 764 input and simple pattern matching, rather than fixed-field formatting. | |
| 765 For example, most @code{scanf} conversions skip over any amount of | |
| 766 ``white space'' (including spaces, tabs, and newlines) in the input | |
| 767 file, and there is no concept of precision for the numeric input | |
| 768 conversions as there is for the corresponding output conversions. | |
| 769 Ordinarily, non-whitespace characters in the template are expected to | |
| 770 match characters in the input stream exactly. | |
| 771 @cindex conversion specifications (@code{scanf}) | |
| 772 | |
| 773 When a @dfn{matching failure} occurs, @code{scanf} returns immediately, | |
| 774 leaving the first non-matching character as the next character to be | |
| 775 read from the stream, and @code{scanf} returns all the items that were | |
| 776 successfully converted. | |
| 777 @cindex matching failure, in @code{scanf} | |
| 778 | |
| 779 The formatted input functions are not used as frequently as the | |
| 780 formatted output functions. Partly, this is because it takes some care | |
| 781 to use them properly. Another reason is that it is difficult to recover | |
| 782 from a matching error. | |
| 783 | |
| 4167 | 784 @node Input Conversion Syntax |
| 3294 | 785 @subsection Input Conversion Syntax |
| 786 | |
| 787 A @code{scanf} template string is a string that contains ordinary | |
| 788 multibyte characters interspersed with conversion specifications that | |
| 789 start with @samp{%}. | |
| 790 | |
| 791 Any whitespace character in the template causes any number of whitespace | |
| 792 characters in the input stream to be read and discarded. The whitespace | |
| 793 characters that are matched need not be exactly the same whitespace | |
| 794 characters that appear in the template string. For example, write | |
| 795 @samp{ , } in the template to recognize a comma with optional whitespace | |
| 796 before and after. | |
| 797 | |
| 798 Other characters in the template string that are not part of conversion | |
| 799 specifications must match characters in the input stream exactly; if | |
| 800 this is not the case, a matching failure occurs. | |
| 801 | |
| 802 The conversion specifications in a @code{scanf} template string | |
| 803 have the general form: | |
| 804 | |
| 6670 | 805 @example |
| 3294 | 806 % @var{flags} @var{width} @var{type} @var{conversion} |
| 6670 | 807 @end example |
| 3294 | 808 |
| 809 In more detail, an input conversion specification consists of an initial | |
| 810 @samp{%} character followed in sequence by: | |
| 811 | |
| 812 @itemize @bullet | |
| 813 @item | |
| 814 An optional @dfn{flag character} @samp{*}, which says to ignore the text | |
| 815 read for this specification. When @code{scanf} finds a conversion | |
| 816 specification that uses this flag, it reads input as directed by the | |
| 817 rest of the conversion specification, but it discards this input, does | |
| 818 not return any value, and does not increment the count of | |
| 819 successful assignments. | |
| 820 @cindex flag character (@code{scanf}) | |
| 821 | |
| 822 @item | |
| 823 An optional decimal integer that specifies the @dfn{maximum field | |
| 824 width}. Reading of characters from the input stream stops either when | |
| 825 this maximum is reached or when a non-matching character is found, | |
| 826 whichever happens first. Most conversions discard initial whitespace | |
| 827 characters, and these discarded characters don't count towards the | |
| 828 maximum field width. Conversions that do not discard initial whitespace | |
| 829 are explicitly documented. | |
| 830 @cindex maximum field width (@code{scanf}) | |
| 831 | |
| 832 @item | |
| 833 An optional type modifier character. This character is ignored by | |
| 834 Octave's @code{scanf} function, but is recognized to provide | |
| 835 compatibility with the C language @code{scanf}. | |
| 836 | |
| 837 @item | |
| 838 A character that specifies the conversion to be applied. | |
| 839 @end itemize | |
| 840 | |
| 841 The exact options that are permitted and how they are interpreted vary | |
| 842 between the different conversion specifiers. See the descriptions of the | |
| 843 individual conversions for information about the particular options that | |
| 844 they allow. | |
| 845 | |
| 4167 | 846 @node Table of Input Conversions |
| 3294 | 847 @subsection Table of Input Conversions |
| 848 @cindex input conversions, for @code{scanf} | |
| 849 | |
| 850 Here is a table that summarizes the various conversion specifications: | |
| 851 | |
| 852 @table @asis | |
| 853 @item @samp{%d} | |
| 854 Matches an optionally signed integer written in decimal. @xref{Numeric | |
| 855 Input Conversions}. | |
| 856 | |
| 857 @item @samp{%i} | |
| 858 Matches an optionally signed integer in any of the formats that the C | |
| 859 language defines for specifying an integer constant. @xref{Numeric | |
| 860 Input Conversions}. | |
| 861 | |
| 862 @item @samp{%o} | |
| 863 Matches an unsigned integer written in octal radix. | |
| 864 @xref{Numeric Input Conversions}. | |
| 865 | |
| 866 @item @samp{%u} | |
| 867 Matches an unsigned integer written in decimal radix. | |
| 868 @xref{Numeric Input Conversions}. | |
| 869 | |
| 870 @item @samp{%x}, @samp{%X} | |
| 871 Matches an unsigned integer written in hexadecimal radix. | |
| 872 @xref{Numeric Input Conversions}. | |
| 873 | |
| 874 @item @samp{%e}, @samp{%f}, @samp{%g}, @samp{%E}, @samp{%G} | |
| 875 Matches an optionally signed floating-point number. @xref{Numeric Input | |
| 876 Conversions}. | |
| 877 | |
| 878 @item @samp{%s} | |
| 879 Matches a string containing only non-whitespace characters. | |
| 880 @xref{String Input Conversions}. | |
| 881 | |
| 882 @item @samp{%c} | |
| 883 Matches a string of one or more characters; the number of characters | |
| 884 read is controlled by the maximum field width given for the conversion. | |
| 885 @xref{String Input Conversions}. | |
| 886 | |
| 887 @item @samp{%%} | |
| 888 This matches a literal @samp{%} character in the input stream. No | |
| 889 corresponding argument is used. | |
| 890 @end table | |
| 891 | |
| 892 If the syntax of a conversion specification is invalid, the behavior is | |
| 893 undefined. If there aren't enough function arguments provided to supply | |
| 894 addresses for all the conversion specifications in the template strings | |
| 895 that perform assignments, or if the arguments are not of the correct | |
| 896 types, the behavior is also undefined. On the other hand, extra | |
| 897 arguments are simply ignored. | |
| 898 | |
| 4167 | 899 @node Numeric Input Conversions |
| 3294 | 900 @subsection Numeric Input Conversions |
| 901 | |
| 902 This section describes the @code{scanf} conversions for reading numeric | |
| 903 values. | |
| 904 | |
| 905 The @samp{%d} conversion matches an optionally signed integer in decimal | |
| 906 radix. | |
| 907 | |
| 908 The @samp{%i} conversion matches an optionally signed integer in any of | |
| 909 the formats that the C language defines for specifying an integer | |
| 910 constant. | |
| 911 | |
| 912 For example, any of the strings @samp{10}, @samp{0xa}, or @samp{012} | |
| 913 could be read in as integers under the @samp{%i} conversion. Each of | |
| 914 these specifies a number with decimal value @code{10}. | |
| 915 | |
| 916 The @samp{%o}, @samp{%u}, and @samp{%x} conversions match unsigned | |
| 917 integers in octal, decimal, and hexadecimal radices, respectively. | |
| 918 | |
| 919 The @samp{%X} conversion is identical to the @samp{%x} conversion. They | |
| 920 both permit either uppercase or lowercase letters to be used as digits. | |
| 921 | |
| 922 Unlike the C language @code{scanf}, Octave ignores the @samp{h}, | |
| 923 @samp{l}, and @samp{L} modifiers. | |
| 924 | |
| 4167 | 925 @node String Input Conversions |
| 3294 | 926 @subsection String Input Conversions |
| 927 | |
| 928 This section describes the @code{scanf} input conversions for reading | |
| 929 string and character values: @samp{%s} and @samp{%c}. | |
| 930 | |
| 931 The @samp{%c} conversion is the simplest: it matches a fixed number of | |
| 932 characters, always. The maximum field with says how many characters to | |
| 933 read; if you don't specify the maximum, the default is 1. This | |
| 934 conversion does not skip over initial whitespace characters. It reads | |
| 935 precisely the next @var{n} characters, and fails if it cannot get that | |
| 936 many. | |
| 937 | |
| 938 The @samp{%s} conversion matches a string of non-whitespace characters. | |
| 939 It skips and discards initial whitespace, but stops when it encounters | |
| 940 more whitespace after having read something. | |
| 941 | |
| 942 For example, reading the input: | |
| 943 | |
| 6670 | 944 @example |
| 3294 | 945 hello, world |
| 6670 | 946 @end example |
| 3294 | 947 |
| 948 @noindent | |
| 949 with the conversion @samp{%10c} produces @code{" hello, wo"}, but | |
| 950 reading the same input with the conversion @samp{%10s} produces | |
| 951 @code{"hello,"}. | |
| 952 | |
| 4167 | 953 @node Binary I/O |
| 3294 | 954 @subsection Binary I/O |
| 955 | |
| 956 Octave can read and write binary data using the functions @code{fread} | |
| 957 and @code{fwrite}, which are patterned after the standard C functions | |
| 6939 | 958 with the same names. They are able to automatically swap the byte order |
| 959 of integer data and convert among the supported floating point formats | |
| 3294 | 960 as the data are read. |
| 961 | |
| 3372 | 962 @DOCSTRING(fread) |
| 3294 | 963 |
| 3372 | 964 @DOCSTRING(fwrite) |
| 3294 | 965 |
| 4167 | 966 @node Temporary Files |
| 3294 | 967 @subsection Temporary Files |
| 968 | |
| 6666 | 969 Sometimes one needs to write data to a file that is only temporary. |
| 970 This is most commonly used when an external program launched from | |
| 971 within Octave needs to access data. When Octave exits all temporary | |
| 972 files will be deleted, so this step need not be executed manually. | |
| 973 | |
| 4328 | 974 @DOCSTRING(mkstemp) |
| 975 | |
| 976 @DOCSTRING(tmpfile) | |
| 977 | |
| 3372 | 978 @DOCSTRING(tmpnam) |
| 3294 | 979 |
| 4167 | 980 @node EOF and Errors |
| 3294 | 981 @subsection End of File and Errors |
| 982 | |
| 6666 | 983 Once a file has been opened its status can be acquired. As an example |
| 984 the @code{feof} functions determines if the end of the file has been | |
| 985 reached. This can be very useful when reading small parts of a file | |
| 986 at a time. The following example shows how to read one line at a time | |
| 987 from a file until the end has been reached. | |
| 988 | |
| 989 @example | |
| 990 filename = "myfile.txt"; | |
| 991 fid = fopen (filename, "r"); | |
| 992 while (! feof (fid) ) | |
| 993 text_line = fgetl (fid); | |
| 994 endwhile | |
| 995 fclose (fid); | |
| 996 @end example | |
| 997 | |
| 998 @noindent | |
| 999 Note that in some situations it is more efficient to read the entire | |
| 1000 contents of a file and then process it, than it is to read it line by | |
| 1001 line. This has the potential advantage of removing the loop in the | |
| 1002 above code. | |
| 1003 | |
| 3372 | 1004 @DOCSTRING(feof) |
| 3294 | 1005 |
| 3372 | 1006 @DOCSTRING(ferror) |
| 3294 | 1007 |
| 3372 | 1008 @DOCSTRING(freport) |
| 3294 | 1009 |
| 4167 | 1010 @node File Positioning |
| 3294 | 1011 @subsection File Positioning |
| 1012 | |
| 1013 Three functions are available for setting and determining the position of | |
| 1014 the file pointer for a given file. | |
| 1015 | |
| 3372 | 1016 @DOCSTRING(ftell) |
| 1017 | |
| 1018 @DOCSTRING(fseek) | |
| 3294 | 1019 |
| 3372 | 1020 @DOCSTRING(SEEK_SET) |
| 3294 | 1021 |
| 3372 | 1022 @DOCSTRING(frewind) |
| 3294 | 1023 |
| 1024 The following example stores the current file position in the variable | |
| 1025 @code{marker}, moves the pointer to the beginning of the file, reads | |
| 1026 four characters, and then returns to the original position. | |
| 1027 | |
| 1028 @example | |
| 1029 marker = ftell (myfile); | |
| 1030 frewind (myfile); | |
| 1031 fourch = fgets (myfile, 4); | |
| 1032 fseek (myfile, marker, SEEK_SET); | |
| 1033 @end example | |
| 1034 |