May i know the difference between these initializations?

  • Thread starter Thread starter shermaine80
  • Start date Start date
  • Tags Tags
    Difference
AI Thread Summary
The discussion clarifies the differences between two C declarations: `char a[] = "string literal"` and `char *p = "string literal"`. The array `a` allocates memory for the string literal, while the pointer `p` points to a memory address where the string is stored. It is noted that `sizeof(a)` returns the total size of the array, including the null terminator, while `sizeof(p)` returns the size of the pointer itself, typically 4 bytes. This distinction is crucial when dynamically copying strings, as demonstrated in examples where using the correct size with `malloc` is essential to avoid truncation. The conversation emphasizes the importance of understanding these differences for effective memory management in C programming, highlighting that while arrays and pointers can behave similarly in many contexts, their underlying mechanics and implications for memory allocation differ significantly. Additionally, the discussion touches on the balance between writing efficient code and ensuring clarity in coding practices.
shermaine80
Messages
30
Reaction score
0
May i know the difference between

(1) char a[] = "string literal"
(2) char *p = "string literal"

char a[] is a array which will include the word "string literal"
whilw char *p is a pointer that points to a address that store the words "string literal"?

Is that correct? Please advise.
 
Technology news on Phys.org
I believe an array type is effectively the same thing as a pointer constant. (not a constant pointer!)

i.e. these two statements mean exactly the same thing

char a[] = something;
char *const a = something;


Functionally, going back to your original example, it simply means that p = a is a valid assignment, because you're allowed to change where p points, but a = p is not, because you're not allowed to change where a points.
 
Last edited:
Hurkyl said:
I believe an array type is effectively the same thing as a pointer constant. (not a constant pointer!)

i.e. these two statements mean exactly the same thing

char a[] = "something";
char* const b = "something";


Functionally, going back to your original example, it simply means that p = a is a valid assignment, because you're allowed to change where p points, but a = p is not, because you're not allowed to change where a points.
Actually there is a subtle difference between a and b.

sizeof(a) is 10 but sizeof(b) is 4 (typically, in a compiler where chars are one byte ("something" is 9 chars plus a NUL) and pointers are 4 bytes).

But in most other contexts, a and b behave identically.
 
And sizeof does make a difference!

For example, let's try to make a copy of each string dynamically.

Code:
    char a[] = "1 String Literal";
    char *a_p = malloc (sizeof (char) * sizeof (a));
    memcpy (a_p, a, sizeof (char) * sizeof (a));
    printf ("%s\n", a_p);
    free (a_p);

Perfect! It works.

Now let's make a copy of the other string.

Code:
    char *p = "2 String Literal";
    char *p_p = malloc (sizeof (char) * sizeof (p));
    memcpy (p_p, p, sizeof (char) * sizeof (p));
    printf ("%s\n", p_p);
    free (p_p);

Uh oh! It only outputs the first four characters!

Oh? But can't we just fix it by using the correct sizeof?

Code:
    char a[] = "1 String Literal";
    char *p = "2 String Literal";
    char *p_p = malloc (sizeof (char) * sizeof (a));
    memcpy (p_p, p, sizeof (char) * sizeof (a));
    printf ("%s\n", p_p);
    free (p_p);

Hurray! It works.

Now... in a real-world situation, you will not have an alternate initialization with the exact same number of characters to use a sizeof on. In that case, further methods can be used to acquire the correct size. Such as strlen under the string.h library, for example.
 
Last edited:
Sane said:
Code:
    char *a_p = malloc (sizeof (char) * sizeof (a));
By the way, sizeof(char) is always 1.

(And even if it wasn't, the correct formulation would still be char* a_p = malloc(sizeof(a));)
 
Yes, you are right. However, I was trying to be as clear as possible.

Half of programming is knowing how to write efficiently and elegantly, the other half is showing clear and concise intentions with your code. This was an example of choosing to go with the latter, readability.
 
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
I tried a web search "the loss of programming ", and found an article saying that all aspects of writing, developing, and testing software programs will one day all be handled through artificial intelligence. One must wonder then, who is responsible. WHO is responsible for any problems, bugs, deficiencies, or whatever malfunctions which the programs make their users endure? Things may work wrong however the "wrong" happens. AI needs to fix the problems for the users. Any way to...

Similar threads

Back
Top