Heap File Allocation:?

[Benzina]

Im following some examples of opening dialog for a builder of hexedit files. Here the code I dont know why the HeapAlloc is used!

void* locate(size_t size){
	return HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, size);
}

Here the OpenFIleDialog:

        WCHAR curdir[MAX_PATH];
	WCHAR *filepath = (WCHAR*)locate(MAX_PATH * sizeof(WCHAR));
	GetCurrentDirectoryW(sizeof(curdir), curdir);
	OPENFILENAMEW ofn;

And in the part of saving:

DWORD fileSize = GetFileSize(hFile, NULL), read;BYTE* pByte = (BYTE*)locate(fileSize);
ReadFile(hFile, pByte, fileSize, &read, 0);

Thx Again guys!

[laserlight]

Here the code I dont know why the HeapAlloc is used!

I would expect it to be used when dynamic memory is required or at least convenient, or when stack memory is expected to be insufficient. So examine the code and see whether these apply.

By the way, did you retype the code? locate sounds like an odd name for the function; perhaps it was meant to be named allocate.

Here the OpenFIleDialog:

There's insufficient information to tell you why locate was used, and hence to tell you why HeapAlloc was used: locate was used to allocate memory for filepath, but the usage of filepath was not shown.

And in the part of saving:

Here it makes sense: you want to allocate memory corresponding to fileSize in order to read the corresponding number of bytes. fileSize is of course can vary at runtime, hence HeapAlloc is appropriate since you thus need dynamic memory allocation.

[Benzina]

By the way, did you retype the code? locate sounds like an odd name for the function; perhaps it was meant to be named allocate.

It isnt my code.

There's insufficient information to tell you why locate was used, and hence to tell you why HeapAlloc was used: locate was used to allocate memory for filepath, but the usage of filepath was not shown.

Here you have mroe code. Its the file opening. But I dont know why it allocates in the Heap?

WCHAR curdir[MAX_PATH];
	WCHAR *filepath = (WCHAR*)locate(MAX_PATH * sizeof(WCHAR));
	GetCurrentDirectoryW(sizeof(curdir), curdir);
	OPENFILENAMEW ofn;
	memset(&ofn, 0, sizeof(OPENFILENAME));
	ofn.lpstrInitialDir = curdir;
	ofn.lStructSize = sizeof(ofn);
	ofn.lpstrFile = filepath;
	*(ofn.lpstrFile) = 0;

[laserlight]

It isnt my code.

Of course. Whose code is it?

But I dont know why it allocates in the Heap?

Probably because it must outlive the scope of the function. I'm not familiar with this API, but in modern C++ we are unlikely to do things this way: we would be making use of RAII instead.

[Benzina]

Its an old Russian Crypter based on RC4.