C / C++ / MFC

Iain Clarke wrote:

So, &array is a pointer to a pointer to chars.

int values[] = { 10, 20, 30, 40, 55, 60, 70, 80, 90, 100 };
int (*pval)[10] = &values;
wcout << *pval[0] << endl;
// or
wcout << **pval << endl;

  wcout << *(*pval + 1) << endl;
  wcout << *(pval[0] + 1) << endl;

George_George wrote:

Sometimes, I noticed that we either use,

1. array (buf)
or use,
2. &array (&buf)
or use
3. &array[0] (&buf[0])

DavidCrow wrote:

1. array (buf)

array

buf

CPallini wrote:

If it stands then the syntax (apart of case (2)) it is used quite a lot.

char array[] = "hello world";

printf("%s\n", array);

printf("%s\n", &array);

printf("%s\n", &array[0]);

DavidCrow wrote:

But none of array(buf), &array(&buf), or &array[0](&buf[0]) are correct.

array(buf)

a number is even (odd) if, divided by two, gives 0 (1) as reminder.

wchar_t me[] = L"George Jackson\n";

wprintf(me);
wprintf(&me[0]);
wprintf(&me); // Won't compile: expects const wchar_t* not wchar_t (*)[16]

wchar_t you[] = L"George Jackson\n";
wprintf(L"%s\n", you);
wprintf(L"%s\n", &you[0]);
wprintf(L"%s\n", &you);

#include <iostream>
#include <string>
 
using namespace std;
 
int _tmain(int argc, _TCHAR* argv[])
{
	wchar_t me[] = L"George Jackson\n";
 
	wcout << me << endl;
	wcout << &me[0] << endl;
	wcout << &me << endl; // You get the address of "me";
 
	wchar_t *me_ptr = me;
	wcout << me_ptr << endl;
 	
	me_ptr = &me[0];
	wcout << me_ptr << endl;
 	
	//me_ptr = &me; // Does not compile
	wchar_t (*me2_ptr)[16] = &me;
	wcout << *me2_ptr << endl;
 
	return 0;
}

void print_myself(wchar_t* myself)
{
	wcout << myself << endl;
}
 
int _tmain(int argc, _TCHAR* argv[])
{
	wchar_t myself[] = L"George Jackson";
	wchar_t (*myself_ptr)[15] = &myself;
	print_myself(*myself_ptr);
	 
	return 0;
}

int main(int argc, _TCHAR* argv[])
{
	
	char a[]="hello world";

	char * p = a;
	char * q = &a[0];
	char * r = &a;

	printf("%x %x %x\n", p, q, r);
	getchar();
}

	char * p = a;
00413392  lea         eax,[ebp-14h] 
00413395  mov         dword ptr [ebp-20h],eax 
	char * q = &a[0];
00413398  lea         eax,[ebp-14h] 
0041339B  mov         dword ptr [ebp-2Ch],eax 
	char * r = &a;
0041339E  lea         eax,[ebp-14h] 
004133A1  mov         dword ptr [ebp-38h],eax 

char a[5];
char *p;
p = a;
printf("p=%x, &p=%x\n); 
printf("a=%x, &a=%x\n");

p=12ff58 &p=12ff4c
a=12ff58 &a=12ff58

#include <iostream>
#include <string>
 
using namespace std;
 
void print_myself(wchar_t* myself)
{
	wcout << myself << endl;
}
 
int _tmain(int argc, _TCHAR* argv[])
{
	wchar_t myself[] = L"George Jackson";
 
	print_myself(myself);
	print_myself(&myself[0]);
	 
	// wchar_t (*myself_ptr)[15] = &myself;
	print_myself(&myself); // Won't compile in C++ as is.
 
	return 0;
}

George L. Jackson wrote:

Was I being dogmatic?

My point is that &array seems to work okay with formatted output but may not work in other situations. &array in C++ is a different type than arrar and &array[0], and behaves differently. Yes, they all return the same address; but, remember, C is no longer a true subset of C++ since there are now too many gotchas.

#include <iostream>
#include <string>

using namespace std;

void print_myself(wchar_t* myself)
{
wcout << myself << endl;
}

int _tmain(int argc, _TCHAR* argv[])
{
wchar_t myself[] = L"George Jackson";

print_myself(myself);
print_myself(&myself[0]);

// wchar_t (*myself_ptr)[15] = &myself;
print_myself(&myself); // Won't compile in C++ as is.

return 0;
}

Thus, it should not even be an alternative to array and &array[0].

George L. Jackson wrote:

Thanks for the discussion.

CPallini wrote:

...this has nothing to do with the core of the original note...