I agree w/ JP, although I've found that the real benefit is to myself as a coder: I have a bunch of commonly used routines (database access and dynamic list creation) that are in a .lib. I tested the code quite rigorously, statically link to it, and rest assured knowing that the code is solid and I don't have to reinvent the wheel when I create a new app. As I find new routines that are being reimplemented from one app to the next, I test them and roll 'em into the library.
Cheers, -DGA PS: And yes, I still test the resulting code rigorously ;P > Primarily, the benefit is that several apps can share > those routines. So, if you create several apps that > share functionality, and if people are likely to > install more than one of those apps on a single > device, then you can save them some space by putting > the shared functions in the library. > > The main downside (though you only asked for benefits) > is that some users appear to have difficulty > installing multiple files on their handheld and none > of your apps will work unless the library is there. > Plus, you have to make sure the library gets deleted > when your app gets deleted, but not if another app on > the device needs it. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
