This is a lame way to do it, but I've run across the same problem and haven't come upon a better solution. In a debug build of your lib, you could require any app that will use your shared lib to init your library by calling a lib-defined init function which gets passed a valid alert ID. If the lib user tries to call a function w/o first initing the lib w/ an alert ID, inform the developer they need to provide an alert box (or include a resource file w/ the alert defined and provided by the lib developer).
Again, not a clean solution, but it will work. I'd love to hear other suggestions. Cheers, -DGA -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
