Changes between Version 1 and Version 5 of Ticket #167


Ignore:
Timestamp:
10/26/17 12:50:58 (22 months ago)
Author:
Dave.Allured
Comment:

I removed that sentence. However I feel that either there should be a warning about possible interpretation, or else a sufficient definition of "interpreted as unsigned" should be added. I would be okay dropping the issue if you think this is sufficient.

Please feel free to directly modify the ticket and insert your own language.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #167

    • Property Type changed from defect to enhancement
    • Property Cc zender@… added
  • Ticket #167 – Description

    v1 v5  
    1919by using the NUG convention of indicating the unsigned
    2020range using the valid_min, valid_max, or valid_range
    21 attributes.  However, the translation between signed and
    22 unsigned values is not well defined, and subject to
    23 interpretation.  This usage is deprecated as of CF version
     21attributes.  This usage is deprecated as of CF version
    24221.8.  Unsigned integer data should be stored with a signed
    2523numeric type of sufficient range and precision, or with native unsigned