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

6.1.4UNSIGNED SMALLINT

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

  • In C, the “unsigned short” data type.
  • In C++, the “unsigned short” data type.
  • In Java6, the “short” data type (or corresponding wrapper class “Short”).
  • In Python, the “uint16” NumPy data type.
  • In C#, the “UInt16” data type (or corresponding alias “ushort”).
  • In Fortran7, the “INTEGER(KIND = 2)” data type.
  • In R8, the “integer” data type.
  • In MATLAB, the “uint16” 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 provide a data type that stores values between 0 and 65,535 using exactly 2 bytes of memory. As a substitute, the R “integer” data type may be used, at the cost of increased memory usage (as it occupies 4 bytes of memory) and lower performance (as byte alignment must be performed by HDFql). ↩