Changes between Version 6 and Version 7 of FdoDataValueTypeConversion


Ignore:
Timestamp:
Oct 19, 2007, 9:30:42 AM (12 years ago)
Author:
gregboone
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FdoDataValueTypeConversion

    v6 v7  
    1010Data value type conversions are not always trivial and the supporting runtime functions sometimes differ between Win32 and Linux (e.g. converting between string and int64). Implementing these conversions in different places leads to the following problems:
    1111
    12 • there is no consistent handling of type conversions. For example, different parts of FDO might handle overflows (value is not valid for the destination type) differently [[br]]
    13 • code duplication. More expensive maintenance if the same fix has to be applied in multiple places (this can easily happen when the type conversion code is cloned to different places)[[br]]
    14 • more difficult for developers to find the type conversion functions currently available, since these can be in various places[[br]]
     12        • there is no consistent handling of type conversions. For example, different parts of FDO might handle overflows (value is not valid for the destination type) differently [[br]]
     13        • code duplication. More expensive maintenance if the same fix has to be applied in multiple places (this can easily happen when the type conversion code is cloned to different places)[[br]]
     14        • more difficult for developers to find the type conversion functions currently available, since these can be in various places[[br]]
    1515
    1616Data values are encapsulated in the !FdoDataValue class and its derivations. There is a derivation for each data type supported by FDO. Example data types include various integer types (8bit, 16bit, 32bit, 64bit), string and datetime.