Changes between Version 10 and Version 12 of Ticket #166


Ignore:
Timestamp:
10/24/17 10:42:06 (22 months ago)
Author:
zender
Comment:

Done. To maintain consensus on the primary purpose of this ticket, adding new integer types, I think we must comply with Dave's suggestion to move all discussion of, and any changes to, treatment of unsigned types in CDF1 and CDF2 to new ticket #167.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #166 – Description

    v10 v12  
    48482.2.1  Unsigned Integers
    4949
    50 It is possible to treat the byte and short types as unsigned by using the NUG
    51 convention of indicating the unsigned range using the valid_min, valid_max,
    52 or valid_range attributes. This usage is deprecated except when the
    53 version of netCDF being used does not support unsigned types.
     50[Original wording, unchanged]  It is possible to treat
     51the byte type as unsigned by using the NUG convention of
     52indicating the unsigned range using the valid_min,
     53valid_max, or valid_range attributes.
    5454
    55552.2.2  Character Strings