On Tue, 18 Nov 2003 13:03:50 +0300, Dmitry wrote: In the future, when 10K parts come up, I'm going to rewrite malloc in the following way: - The memory above 2K (5K and 8K in 16xx devices) will be called '.heap'. - Compiler itself wont be allowed to allocate memory there without user's intrusion. - malloc()'s bottom will be heap's bottom, which will be calculated as a .heap bottom + numb of user allocated bytes there. - malloc() calls for any other devices will return zero.
suggestions? cheers, ~d Making the top-of-stack and start-of-heap start at the same memory location sounds fine by me. Please however, allow that location to be easily set by the user without having to modify any of the standard files (linker control, startup, etc.). -Bill Knight R O SoftWare
