Tamas Rudnai wrote:
>> >> FWIW, we use dynamic memory allocation in all of our current projects
>> >> (on 24H and 33F).
>> >>
>> >> ...
>> >>
>> >> Memory gets allocated during initialization and doesn't change.
>> >
>> > These two statements seem to be at odds with each other.
>>
>> How's so?
>>
> If memory is allocated during initialization, then you have no dynamic
> memory allocation.

Not true. I am working on a project right now, where calloc() is used to 
allocate memory for structures and linked lists during initialization. These 
variables stay in memory (they don't get deallocated). This approach is a 
lot more flexible than using static variables. For instance, I can easily 
change the number of objects in a linked list if I need to, and in the 
future (when the parser is ready) users will be able to add/remove objects 
at runtime.

Of course there are other objects that get created and destroyed all the 
time (for example, message structures).

Hm, maybe we interpret "initialization" differently? I mean the code that 
sets everything up before the program starts executing the main loop, not 
the compiler's init code.

Vitaliy 

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist