[nkasei28]

Hi,

Why would this not work? And what is the right thing to do.

        int x,y,z;

	printf("Enter three integers: ");
	scanf("%d %d %d",&x,&y,&z);
        
	p[0]=&x; //syntax error here
	p[1]=&y; //and here
	p[2]=&z; //and here

[ButchDean]

Assuming your array is of the same type, just remove the '&' for your assignments.

[sepp2k]

There is no way those lines would cause a syntax error unless there's a syntax error elsewhere in your file. They might cause a type error though if p is neither an array of pointers to int nor a pointer to pointers to int.

The right thing to do would depend on what exactly it is you're trying to do.

[ButchDean]

Yes it does Sepp2k.

Assuming an int array as I said before, you get a cannot convert from int* to int.

[sepp2k]

ButchDean, on 02 January 2013 - 09:23 PM, said:

Yes it does Sepp2k.

Assuming an int array as I said before, you get a cannot convert from int* to int.

I'm not sure whether you're agreeing with me ("Yes, as you said, it does cause a type error if it's an int array") or disagreeing with me ("Yes, it does cause a syntax error").

In the latter case: not being able to convert from one type to another is not a syntax error - it's basically the definition of a type error.

In the former case: thank you for your support :-)

[ButchDean]

Oh you're talking about 'semantics'. I took it as you were saying there was no error at all when there was.

[sepp2k]

I specifically said that there will be a type error if "p is neither an array of pointers to int nor a pointer to pointers to int". I don't see how that could be interpreted as "there is no error at all".

Anyway, misunderstanding cleared.

[Skydiver]

Don't forget array of pointers to void.

[ButchDean]

Well, the fact that there was a misunderstanding means that there was scope for such. You said it 'might' cause a type error, there is no 'might' because it clearly does.

I didn't even run the code and I knew for sure there was an error.

[sepp2k]

ButchDean, on 02 January 2013 - 09:47 PM, said:

You said it 'might' cause a type error, there is no 'might' because it clearly does.

If p is an array of int pointers, a pointer to int pointers or, as Skydiver pointed out, an array of or pointer to void pointers, then the code posted by the OP will not cause a type error (or any other type of error). That's why I said "might".

[ButchDean]

Then make it clear as I did. Simple really.