the 3.5 version of DateToDOWDMFormat is not backward compatible with apps written for older OS versions. at least, not in Debug ROMs. i can understand this in Debug ROMs, but i noticed that in each new OS version, its "minimum buffer size" keeps growing. this seems like a backward compatibility problem.
the 2.0 SDK says DateToDOWDMFormat expects the target string to "be of length timeStringLength" (==9). the 3.3 SDK says DateToDOWDMFormat expects the target string to "be of length longDateStrLength" (==15). i decided to play it safe in my app, and i used longDateStrLength, however this blows up in OS 3.5. what concerns me is that this does not consistently cause problems with the Debug ROM, so it's not just a matter of the Debug ROM over-aggressively filling memory to flush out errors (if that were true, it should be 100% consistent). this makes me suspicious that there's actually a bona fide bug in the API. if someone from Palm wants to follow up with me privately, i can provide exact repro steps if this is not a known issue, or is not obvious from examining the source. // chris -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
