HDFql Reference Manual v2.6.0
/
Manual/6 Language/6.1 Data Types

6.1.6UNSIGNED INT

The HDFql UNSIGNED INT data type stores values between 0 and 4,294,967,295 and occupies 4 bytes in memory. It represents the data type of an HDF5 H5T_NATIVE_UINT dataset/attribute or of a result set that stores elements of this type (which can be retrieved using the HDFQL_CURSOR_GET_UNSIGNED_INT function when working with cursors). Depending on the programming language supported by HDFql, the UNSIGNED INT data type is represented by:

  • In C, the “unsigned int” data type.
  • In C++, the “unsigned int” data type.
  • In Java9, the “int” data type (or corresponding wrapper class “Integer”).
  • In Python, the “uint32” NumPy data type.
  • In C#, the “UInt32” data type (or corresponding alias “uint”).
  • In Fortran10, the “INTEGER(KIND = 4)” or “INTEGER” data type.
  • In R11, the “integer” data type.
  • In MATLAB, the “uint32” data type.

Notes

  1. By design, Java does not support unsigned data types. Therefore, the programmer is responsible for converting a signed number to its equivalent unsigned representation in Java. ↩
  2. Although there have been some efforts to introduce unsigned data types in Fortran, none are currently standardized. Therefore, the programmer is responsible for converting a signed number to its equivalent unsigned representation in Fortran. ↩
  3. By design, R does not support unsigned data types. Therefore, the programmer is responsible for converting a signed number to its equivalent unsigned representation in R. ↩