Hello All, Sorry for the long inclusion, but someone previously mentioned that context is important... If you are using the NewFloatMgr.lib that is included with CW/Palm R5, you should stop and rebuild with the library that is on CW/Palm R4. The library, which is provided by Palm and included on our CD, was not built correctly. I'll spare you the details, but if you disassemble the two libraries, you will notice the JSRs for the R4 and R5 versions are different. This change should affect very few of you. After all, it took four months to surface in the first place. It is an issue if you are targeting Palm OS 1.0 users, have floating point code, and you are including NewFloatMgr.lib from R5 in your projects. -E > -----Original Message----- > From: Richard Wagner [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 24, 1999 9:53 AM > To: [EMAIL PROTECTED] > Cc: 'Eric Cloninger' > Subject: RE: CWR5- Floating Point Library & FlpFToA() - Argghh! > > > Steve, > > Thanks for the suggestion. I had already tried this and it produced very > interesting results. I didn't want to bring it up before since it might > confuse the issue. With those #defines in there the compiler produces: > err = FlpFToA(theComp.fd, szTemp); > 1006A36A: 486EFFD2 pea -46(a6) > 1006A36E: 2F2EFFF4 move.l -12(a6),-(sp) > 1006A372: 2F2EFFF0 move.l -16(a6),-(sp) > 1006A376: 4EBAE2CE jsr *-7472 ; 0x10068646 > > Which should work, right? Nope. The JSR goes off into a library routine, > which runs for about 10 lines and then done this: > 10068680: 4EB9000002AC jsr 0x000002ac ; 0x000002ac > > Oops! 02ac is just garbage memory and the whole thing tanks right there. > This sounds like a problem with the library, but since Metrowerks doesn't > include the source I can't track it down (not much of an assembly > programmer). > > Until now, having another build for Pilot users has been trivial and keeps > my early customers (some of whom still have Pilots) happy. > > Thanks for the help! > Rick Wagner >
