(octave.info)Table of Input Conversions

---

Next: Numeric Input Conversions Prev: Input Conversion Syntax Up: C-Style I/O Functions

---

Enter node , (file) or (file)node

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.  Note:
     Numeric Input Conversions.

‘%i’
     Matches an optionally signed integer in any of the formats that the
     C language defines for specifying an integer constant.  Note:
     Numeric Input Conversions.

‘%o’
     Matches an unsigned integer written in octal radix.  Note: Numeric
     Input Conversions.

‘%u’
     Matches an unsigned integer written in decimal radix.  Note:
     Numeric Input Conversions.

‘%x’, ‘%X’
     Matches an unsigned integer written in hexadecimal radix.  Note:
     Numeric Input Conversions.

‘%e’, ‘%f’, ‘%g’, ‘%E’, ‘%G’
     Matches an optionally signed floating-point number.  Note: Numeric
     Input Conversions.

‘%s’
     Matches a string containing only non-whitespace characters.  Note:
     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.  Note: 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.