Mike Davis writes:
> my include file is just: .../include/PalmOS/ There is nothing
> indicating the version.
If you have a reasonably vanilla prc-tools installation, you'll see
PalmOS1 and PalmOS2 directories alongside that one. And in fact, PalmOS
will be a symlink to one of those two.
> I'm not speaking of "what OS version..." in terms of an app determing
> that. I am just trying to see how my development environment is
> configured. I suspect that it's still setup for OS 2.0
I realise that's what you are asking. In fact, there's no "suspect"
about it, because the prc-tools 0.5.0 you are using predates OS 3.0 :-).
"How do I know my app will work with a v2.0 Palm Pilot?" is an interesting
question. "Just compile it with the v2 headers" is a nice easy answer for
the developer, but it's bloody hard for the compiler maintainer to support
it. (eg, I'll have to fix the current SDK NewFloatMgr.h header to do the
right thing for gcc programs, and theoretically I ought to do the same
thing to the v2 includes, because that was a feature present in OS v2.
But that's extra work for me, with very questionable value.)
But it also happens to be a misleading answer for the developer. You can
query features to disable your beam menu (etc) if it's not supported on the
user's device, and then your app will work fine on a v2 Pilot even though
it contains v3 systraps that don't exist on that device.
So I think the right thing to do is to use only the latest SDK headers.
You find out whether your app works on OS v2 by thinking and testing.
(Sorry. Your question #2 probably wasn't intended to be asking about
compiler maintainence headaches. But I didn't notice any other
interpretations that made sense...)
John
