Info Catalog octave: Input Conversion Syntax octave: C-Style I/O Functions octave: Numeric Input Conversions

octave: Table of Input Conversions

 
 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.  
      Numeric Input Conversions.
 
 ‘%i’
      Matches an optionally signed integer in any of the formats that the
      C language defines for specifying an integer constant.  
      Numeric Input Conversions.
 
 ‘%o’
      Matches an unsigned integer written in octal radix.  Numeric
      Input Conversions.
 
 ‘%u’
      Matches an unsigned integer written in decimal radix.  
      Numeric Input Conversions.
 
 ‘%x’, ‘%X’
      Matches an unsigned integer written in hexadecimal radix.  
      Numeric Input Conversions.
 
 ‘%e’, ‘%f’, ‘%g’, ‘%E’, ‘%G’
      Matches an optionally signed floating-point number.  Numeric
      Input Conversions.
 
 ‘%s’
      Matches a string containing only non-whitespace characters.  
      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.  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.
 

Info Catalog octave: Input Conversion Syntax octave: C-Style I/O Functions octave: Numeric Input Conversions