Memory shortage in Turbo C

I'm doing my project in Turbo C++ and it usually runs out of memory.
I'm developing an Image Processing System.
Problem encountered when I try to copy the pixel information of 24 bit BMP file into
a dynamically allocated 2D array.
There are no coding bugs since it's working fine on smaller size images(I found that it's working
for images upto 240*240 size).
I want to load images upto 900*900.
How can I do this.
I tried to switch to different memory models in TC but size of Near Heap and Far heap
are almost same in all cases( in point of view of Application requirements).
Please suggest me how can I get rid of this problem.
Thanking

I am afraid that near and far (pointers?) are too archaic for me, but what it does sound like is that you are trying to use too much space on the stack. You may need to allocate space on the heap instead with malloc and friends, (and free the memory when you are done).

You have two major sources of memory in TC, the stack, and the heap.

If you can't get enough memory out of the heap, then try putting your other variables onto the stack, and see how that works.

Alternatively, put your 2D array onto the stack by making it non-dynamic, and try to free up the rest of the stack, as much as possible.

Also, you can change your program to allow it to work with just a portion of the whole image, at any one time. Maybe do a quarter of it at a time?

Bottom line is, TC (and I'm a big TC user still), is not well suited for larger memory demands. Move the program over to MS Visual C Express (it's free), or one of the other 32 bit C compilers.
That's what I do with my larger programs. I love TC, but ... :)

Quote:

---

Originally Posted by Adak

You have two major sources of memory in TC, the stack, and the heap.

If you can't get enough memory out of the heap, then try putting your other variables onto the stack, and see how that works.

Alternatively, put your 2D array onto the stack by making it non-dynamic, and try to free up the rest of the stack, as much as possible.

Also, you can change your program to allow it to work with just a portion of the whole image, at any one time. Maybe do a quarter of it at a time?

Bottom line is, TC (and I'm a big TC user still), is not well suited for larger memory demands. Move the program over to MS Visual C Express (it's free), or one of the other 32 bit C compilers.
That's what I do with my larger programs. I love TC, but ... :)

---

The problem is that I've already written almost 300 lines of code and I doubt if it would work nicely on other compilers like u recommended.
And I've no prior experience with other C compilers so tell me
what differences I should expect??

If your code is standard C, it shouldn't matter what compile you're on. If you've got a bunch of system specific / compiler specific stuff scattered around (gotoxy, etc), then yes, you'll have some trouble.


Quzah.

Quote:

---

Originally Posted by gurudeep

The problem is that I've already written almost 300 lines of code and I doubt if it would work nicely on other compilers like u recommended.
And I've no prior experience with other C compilers so tell me
what differences I should expect??

---

that's peanuts! :)

Standard C code will be fine, just be sure to name the file with a .c extension. Check your options and make sure the C compiler is going to be used for all *.c programs. Otherwise, you'll get the C++ compiler, and that you won't like *that* a bit. :)

If you have TC specific stuff, you'll need to use the work-arounds. Like gotoxy() for TC, becomes SetConsoleCursorPosition(), for a console program.

It takes a while, but download the video from MS also, on how to use the Visual C express IDE. And just be patient. You *WILL* be up to speed with it soon. It just takes some practice.

Lots of people here use it, so ask away if you have any questions.

Thanks for help.Now I've fair idea and I think It won't be that troublesome switching to
other compilers.
One of my friend suggested Dev C++.What are your opinion about it??

Dev-C++ is an IDE, not a compiler. The compiler that comes with Dev-C++ (the MinGW port of gcc) is fine, though Dev-C++ itself is rather buggy and has not been updated for years.

For images that size you are going to have to use the HUGE memory model. I still think you are going to be limited to 64KB elements though. As suggested, switching to a more modern compiler is probably a good idea.