Thanks again, Matt. I had the same problem with trying to use #pragma
Segment 1 (space between "Segment" and "1") so that the name would match the
default name that CW supplies. But using #pragma Segment1 (without the
space) did not cause the compiler to map the code into that segment for me.
Instead I just get the startup code. As a result, my application crashes
with memory access errors the first time I try to assign a value to a local
variable. Again, I'd break up my source into different files and use the
feature to segment by file except that this is an open source project with
lots of developers and the majority do not use CW. So I'm making a rather
disruptive change (and possibly messing up the source control system) if I
do that.
Other suggestions?
David
=========================
David Beers
Pikesoft Mobile Computing
www.pikesoft.com
\ * Custom PDA software
\ * Field Data Collection
\ * Wireless Mobile Applications
\ * CRM and Salesforce Automation
> > A quick follow-up question here. Segmenting using #pragma segment is
> > working fine except for one important thing: how to control the order of
> the
> > segments. Specifically, how do you make sure that the functions you
need
> to
> > be in code 1 (PilotMain, eg.) actually land there? The documentation
I've
>
> ?
> If your first segment is named "Segment1"
> and you put
> #pragma segment Segment1
>
> The code should end up in the first segment.
> Check the Segments tab and make sure your first (and possibly only segment
> listed) segment is named "Segment1".
> I think by default it's called "Segment 1". I had to take out the space,
I
> couldn't figure out how to get #pragma segment working if a segment name
> contains spaces.
>
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
