So, has anyone figured out how much code space is required for the resource
approach as opposed to the hard coded method?
It seems often the code required for using resources will be larger than the
string itself.
Ed
----- Original Message -----
From: "Ken Krugler" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, September 20, 2000 11:36 AM
Subject: Re: strings and string lists
> At 12:00am -0700 00-09-20, Palm Developer Forum digest wrote:
> >Subject: strings and string lists
> >From: "Charles Rezsonya" <[EMAIL PROTECTED]>
> >Date: Tue, 19 Sep 2000 13:19:57 -0400
> >X-Message-Number: 52
> >
> >Are there any pro's or con's against using strings&string lists versus
hard
> >coding strings into the app?
>
> In addition to the previous responses, another con to using
> hard-coded strings is that they increase the size of your code
> resource. This can trigger problems with jumps > +/- 32K, and code
> segments > 64K, which would be delayed if string data is contained in
> separate resources.
>
> Of course using hard-coded strings is easier, since you don't need to
> worry about maintaining resource IDs, you don't need to make
> DmGetResource calls, and you don't need to worry about
> locking/unlocking/releasing resources.
>
> In general, though, using resources for string data is considered
> proper coding practice for Palm apps.
>
> -- Ken
>
> Ken Krugler
> TransPac Software, Inc.
> <http://www.transpac.com>
> +1 530-470-9200
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
