On Sat, Jan 10, 2009 at 07:19:38PM -0800, Kent Loobey wrote: >> >> Managed Make 68K C/C++ Project >> Managed Make 68K PNO C/C++ Project > >After Googling around I think PNO may stand for "PACE Normal Objects". > >I found this "PNOs allow you to unleash the power of the ARM processor >on Palm OS 5 devices but they are difficult to build." So I think that PNO >code must be native ARM code. > >So is there a great disadvantage to just using non PNO projects?
Close. PACE is the m68k emulator which runs atop the ARM processor and a PNO is a "Palm Native Object". You're correct that a PNO is a native ARM binary instead of (regular) emulated m68k code. PNOs are essentially self contained objects. You can pass in arguments to process data, but, if I recall correctly, a PNO cannot access global values. Also, a PNO cannot easily execute Palm OS API traps (system calls). Normally, you would use a PNO to work on a block of data where speed is important. For example, the zLib library is available as a PNO and is substantially faster than the m68k version. You pass in a block of data to compress or decompress and you get back a buffer with the result. -- --John Gruenenfelder Systems Manager, MKS Imaging Technology, LLC. Try Weasel Reader for PalmOS -- http://weaselreader.org "This is the most fun I've had without being drenched in the blood of my enemies!" --Sam of Sam & Max -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
