GNU Octave Manual Version 3 by John W. Eaton, David Bateman, Søren Hauberg Paperback (6"x9"), 568 pages ISBN 095461206X RRP £24.95 ($39.95) Get a printed copy>>>

GNU Octave Manual Version 3 Buy the book here >>> support free software

14.2.13 Table of Input Conversions

Here is a table that summarizes the various conversion specifications:

‘%d’

Matches an optionally signed integer written in decimal. See section 14.2.14 Numeric Input Conversions.

‘%i’

Matches an optionally signed integer in any of the formats that the C language defines for specifying an integer constant. See section 14.2.14 Numeric Input Conversions.

‘%o’

Matches an unsigned integer written in octal radix. See section 14.2.14 Numeric Input Conversions.

‘%u’

Matches an unsigned integer written in decimal radix. See section 14.2.14 Numeric Input Conversions.

‘%x’, ‘%X’

Matches an unsigned integer written in hexadecimal radix. See section 14.2.14 Numeric Input Conversions.

‘%e’, ‘%f’, ‘%g’, ‘%E’, ‘%G’

Matches an optionally signed floating-point number. See section 14.2.14 Numeric Input Conversions.

‘%s’

Matches a string containing only non-whitespace characters. See section 14.2.15 String Input Conversions.

‘%c’

Matches a string of one or more characters; the number of characters read is controlled by the maximum field width given for the conversion. See section 14.2.15 String Input Conversions.

‘%%’

This matches a literal ‘%’ character in the input stream. No corresponding argument is used.

If the syntax of a conversion specification is invalid, the behavior is undefined. If there aren't enough function arguments provided to supply addresses for all the conversion specifications in the template strings that perform assignments, or if the arguments are not of the correct types, the behavior is also undefined. On the other hand, extra arguments are simply ignored.