Printable View
Code:#include<stdio.h>
#include<conio.h>
void main()
{
int a[20],i,n,*j;
clrscr();
printf("Enter 5 elements\n ");
for(i=0;i<5;i++){
scanf("%d",&a[i]);
j=&a[i];
}
for(i=0;i<5;i++){
printf("Elelent %d ",a[i]);
printf("address is %u\n",j);
}
getch();
}
i know this code prints only last address,
please rectify to print each value
Lose the j.
Print the address
Code:printf("address is %p\n", (void*)(a + i));
Why not &a[i] ?
Having a a pointer (or a decayed array) and i an int: &a[i] and a + i are exactly the same thing.Quote:
Originally Posted by nonoob
The only reason to choose either one is stylistic: I prefer the last one.
Note that, for the printf() conversion specifier "%p", the cast is required regardless of the style you choose.
Also note that using "%u" with addresses is not garanteed to work (it's Undefined Behaviour).Code:printf("%p\n", (void*)&a[i]);
printf("%p\n", (void*)(a + i));
My comment was directed more to the OP. He used &a[i] without problem in the scanf. So why did he forget about that in the printf?
would you mind making your code clearer by spacing out the code.????
That is not true.Quote:
Originally Posted by qny
Please see 7.21.6.3 and 7.21.6.1 in the C11 Standard.Quote:
Originally Posted by grumpy
7.21.6.3 says that the printf() function behaves like fprintf() (described in 7.21.6.1).
7.21.6.1/8 says that the argument relevant to the conversion specifier p "shall be a pointer to void".
Also 6.2.5/28 says that pointers to void and pointers to any type other than char do not need to share the same representation and alignment: meaning that (on some implementations) a pointer to int and a pointer to void are not interchangeable.
You're assuming that value and representation are the same thing. They are not. %p prints the value of the pointer, not it's representation.
Value and representation are indeed different things. I know that.
Imagine for the sake of argument that instead of void* and int* we're dealing with int and long: the value 42 is valid for both types, however
The value is the same no matter the type however the representations are different. The above code invokes Undefined Behaviour (same as using %p without a void*). On some computers it will print 42; on others it will print 0; on others it will segfault.Code:printf("%d\n", 42L);