Help!Maximum array size in C?

I need to sort a long int array which size at 300000 in C. When I define like this:

# define SIZE 300001
long int array[SIZE]

in my code, complier say that my array is too large.

Anybody know how do expand the limitation? And what's the real limitation?


Thanks a lot


robin

To use large arrays you have to use dynamic memory. Look up malloc and free.

The maximum size of an array is different from machine to machine, depending on how much memory it has.

are you a VB programmer? your array declaration should be :

long int array[SIZE];

works on my machine. I'm not 100% sure about limitations though so i'll leave it for someone else..

Sorry for mis typing.
it shound be array[SIZE].
Shakti ,do you mean that I must use malloc to allocate the memory one by one? Or I can allocate at a time for 300000 long int array? Can you show an example?


Thanks

robin

Perhaps if you said which OS and compiler you were using, we could help further.
300K for a single array seems a bit on the small side for a limitation on a 32 bit machine.

I just use TC as a complier.

OS is windows XP,machine seems good in the school computer lab.

Welcome to the world of 16 years ago. I mean...
Welcome to the world of 16 bits. That is to say...
Get a new compiler.

Quzah.

If you want to use dynamic memory simply declare a pointer to the type you want to allocate in this case int, and call the malloc() function with the argument being the number of bytes you want the "array" to be. In this case you need to get the sizeof a single integer and multiply it by how big you want it to be (i.e. the number of cells):

Code:

---

int* array;
array = malloc(sizeof(int) * SIZE);
if (array == NULL)
{
      fprintf(stderr,"Could not allocate that much memory");
      return 1;
}

/* do something with array */
free(array);

---

Make sure you free anything you malloc'ed otherwise you will get memory leaks.

It won't matter. They'll hit their compiler's 64K limit. Dynamic allocation won't get around that.

Quzah.

Quote:

---

Originally Posted by quzah

Welcome to the world of 16 years ago. I mean...
Welcome to the world of 16 bits. That is to say...
Get a new compiler.

Quzah.

---

so what if it is 16 years old
we are discussing logic behind programs dear.it dosent matter if it is 16 years old or 1 day old. c programming needs C that's it. but i do agree that there will be portability problem. ive started using VC++. but still TC is much better

Quote:

---

Originally Posted by coolshyam

so what if it is 16 years old
we are discussing logic behind programs dear.it dosent matter if it is 16 years old or 1 day old. c programming needs C that's it. but i do agree that there will be portability problem. ive started using VC++. but still TC is much better

---

That's why you're an idiot. Because you don't pay attention to what I just said. It's an old compiler. It is limited by its age. Do you actually know what you scan store in 16 bits? Unsigned? Roughly 64000. OH MY GOD! Does that mean you can't have the number 300001?

You bet your ass you can't, "dear". There's your "logic behind it", "dear".

Quzah.