SafeNum should be written in terms of explicitly sized types like int32_t and int64_t

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • 3.3.2
    • Affects Version/s: None
    • Component/s: Internal Code, Portability
    • None
    • Fully Compatible
    • ALL
    • Platforms 10 (02/19/16)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The current implementation of SafeNum makes unwarranted assumptions about the sizes of the integral types 'int' and 'long long int'. Since SafeNum is explicitly intended to model signed 32-bit and signed 64-bit integers, its interface and implementation should be re-written in terms of the appropriate fixed width integer types: int32_t and int64_t.

              Assignee:
              Waley Chen (Inactive)
              Reporter:
              Andrew Morrow (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: