At 11:46 AM 4/2/99 -0800, you wrote:
>At 9:56 PM -0800 4/1/99, Chris Antos wrote:
>>i hope it's clear that since the objects were not opaque it is a major
>>problem to make them opaque now. so far, Palm has been very good about
>>keeping structs binary compatible for backwards compatibility.
>
>We want to encourage people to start thinking of them as opaque, so we need
>a way to transition.
>
If you really want to do this, for a few of the types you are going to need
to build in a lot more conversion/utility routines. In particular, the
date types and floating point types do not convert to PC formats well at
all (from a sync point of view). If you sync a DateType, you must know how
it is constructed to be able to use it on the PC.
The floating point type support is a joke, even on device.
Example function to print a floating point, rounded to the one decimal place:
_fp_round(flpToNearest); // does nothing
sdwVal = _d_dtou(pRec->fValue);
fRem = _d_add(_d_mul(_d_sub(pRec->fValue, _d_utod(sdwVal)), _d_utod(100)),
_d_utod(5));
sdwRem = _d_dtou(_d_div(fRem, _d_utod(10)));
StrPrintF(acBuf, "%ld.%1ld", sdwVal, sdwRem);
Disclaimer: I'm talking about x86 family PCs. I have no idea if there are
formats on other processors (ok, Macs - but it could be Alphas, blah blah)
