1. Anyone have any experience/opinions about using the STL on the Palm. Specifically, is there a lot of code bloat which makes it not worth it? I wouldn't mind having a nice map and string classes.
The STL bloats the first code segment unnecessarily; use POL's built-in CString and CHash, etc, classes instead. Otherwise you will find yourself running into lots of "16-bit code reference" link errors and doing the dreaded Segment Juggle.
2. I'm thinking of re-writing a large app to take advantage of POL (the app is at a point where it could really do with a good rewrite anyway). Ben appears to be a big fan of POL. Does anyone have any positive or negative experience with writing a large app using POL?
I rewrote a few smaller apps in POL to learn it. It took about 3 days of swimming around in POL documentation before I finally figured out what I was doing. After that point, POL became a huge timesaver. Particularly by reusing its table, form, and string classes. This stuff is very tedious and error-prone to do by hand, as any Palm OS developer will tell you.
Once I knew how POL worked, I wrote a large app from scratch in POL. And another. I wouldn't dream of writing a non-POL application at this point. It's a tremendous timesaver both in terms of reusing/extending its classes and by reducing bugs/maintenance: POL classes are very well-designed and have been revised enough times to be devoid of bugs. No software is bugfree, but this has never been a problem for me with POL.
-Jeff Ishaq
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
