We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I want to allocate memory which I can use as a two dimensional array. But the following code is not working
unsigned char xdata ** memo; unsigned char i = 0; // n is number of rows // size is number of columns memo = (unsigned char xdata **) malloc( n*2 ); for ( ; i < size; i++) memo[i] = (unsigned char xdata *)malloc( size );
memo = new char * [n]; for (int i=0; i < n; i++) memo[i*2] = new char [size];
"I dont want to waste the memory by using static array." So instead you will waste both code & memory with the overheads of dynamic allocation?! Did you follow that link: http://www.keil.com/forum/docs/thread2622.asp "I want to be able to free the memory not needed and allocate only when it is required." Keil's overlay analysis will do this for you - without the need for malloc!
What if I have to sort the char strings? In that case swapping the pointers etc. will be more easy than to physically move the characters. In fact sorting is a major concern in my application that should be fast.
"What if I have to sort the char strings? In that case swapping the pointers etc. will be more easy..." Yes, but that has nothing to do with dynamic allocation, does it? Whether the pointers point to statically- or dynamically-allocated storage makes no difference!
I think you people want to avoid malloc at all costs :) ...but the problem is that I have two applications, notepad & phonebook, that will share the memory. And if one application requires more memory than the other why should I restrict it? It is the user who is to decide in which application to save more entries. And the optimimum technique is to use memory dynamically. Moreover, both applications use different data structures. Perhaps you'll say that 8051 is not meant for such things but I must do it somehow because I don't want to lose the client :) ... And if malloc can help simplify the logic why not use it? And being a developer atleast one should know how to such things...malloc may pose some severe problems but difficult things are not to be put aside :) ... See you later... Regards, aFFAN
"I think you people want to avoid malloc at all costs" As already noted, that is generally a good approach for embedded systems suited to an 8051 What you're doing is not a conventional embedded system for an 8051, and dynamic allocation may well be appropriate to your application - but you hadn't described the application before, so we couldn't tell, could we? Too many people just assume that anything a PC can do will be good on an 8051.