malloc() strings VS array strings

In other words:

Code:

---

char *chosen = malloc(255 * sizeof(chosen));
/* Use string here */
free(chosen);

---

VERSUS

Code:

---

char chosen[255];
/* Use string here */

---

Does it even matter? The only reason to use the first approach with pointers would be to make the program run faster? Wouldn't they be the same speed as far as usage?

This question comes up because I was doing a program that needed a string and I asked myself: "Why am I going like this?"

Code:

---

char *chosen = malloc(255 * sizeof(chosen));

---

For any other reason besides practice? I must ask! I must search for a better reason!

There is no pratical reason in your example to use malloc() instead of an array. malloc()'s reason-for-being is dynamic memory allocation. As such, the parameter you pass to it is usually a variable, not a constant. For instance: char *ptr = malloc(runtime_determined_number);.

The only reason I can think of to use malloc() in your example is to have the flexibility of the pointer (Ever tried array++;? It doesn't work). For instance, you might want to walk through the array. But that's not very good pratice anyway, since you have to find the beginning of the allocated memory again to free() it. A better solution for that would be to have a separate pointer. Something like: char array[255]; char *ptr = array;.

Make sense?

Quote:

---

Originally Posted by itsme86

As such, the parameter you pass to it is usually a variable, not a constant. For instance: char *ptr = malloc(runtime_determined_number);.

---

But you could also do that with a regular array:

Code:

---

char szList[SomeVarible];

---

Quote:

---

Originally Posted by itsme86

The only reason I can think of to use malloc() in your example is to have the flexibility of the pointer (Ever tried array++;? It doesn't work).

---

But you could easily go like this to step through an array:

Code:

---

int i;
for(i=0; i<LENGTH_OF_ARRAY; ++i)
    /* Do stepthrough code here */

---

I need more reason! :(

How about that malloc() requires a syscall to brk()/sbrk() which is slower than a normal array which is all allocated when the program is started. Not to mention that you don't have to bother with calling free() when using arrays; one less chance for a memory leak.

And your method of creating an array of variable size doesn't work in all instances. Example:

Code:

---

{
  char *array = NULL;
  int size;

  printf("How big?\n");
  scanf("%d", &size);
  array = malloc(size);  // Try doing this with an array
  free(array);
}

---

Code:

---

{
  /*char *array = NULL;*/
  int size;

  printf("How big?\n");
  scanf("%d", &size);
  /*array = malloc(size);  // Try doing this with an array */
  char array[size];
  // free(array);
}

---

But I see what you mean lol, :P. Especially if you need to realloc or it's a global array!

another thing to consider is how large the chunk of data needs to be - most systems grant more dynamic storage than stack space...