3d: WindowsAPI: Windows-make: How do we face memories problem: About Visual Studio

 (20200510)
We could count the number of memorization, Qualified.
Anyway, the Lootin threw out all steps in Visual Studio.

(20200509: ) We could include class-vLine and refer: which has Pointter: and has Pointer as Pointer of Pointer: 

#include 
#include 

#include "sender.h"
#include "Print.h"

#include "vPoint.h"
#include "vLine.h"


int setLine(vLine line);
int setLine(vLine* line);
int setLine(vLine** line);

#pragma comment(lib, "Ws2_32.lib")

int main() {

	return 0;
}


int setLine(vLine** line) {

	return 0;
}


int setLine(vLine* line) {

	return 0;
}

int setLine(vLine line) {
	return 0;
}

---

int v3dCalculation::calculation_thread_009() {
	printf("v3dCalculation:: calculation_thread_009 () starts.\r\n");
	calc.Print_Point_Memories();

	// Recognision: 20200508: inside display_threeD_screen_initialize_OnRails:
	//rails_initialization(); inside display_threeD_screen_initialize_OnRails:
	int a001 = display_threeD_screen_initialize_OnRails();
	int a002 = getCreatedLines();
	calc.Print_Point_Memories();
	printf("v3dCalculation:: calculation_thread_009 () ends.\r\n");
	return 1;
}

i: 1753 p: 0134A6F8
i: 1754 p: 0134A298
i: 1755 p: 0134A5E0
i: 1756 p: 0134A2D0
i: 1757 p: 0134A688
i: 1758 p: 0134A6C0
i: 1759 p: 0134A068
i: 1760 p: 0134A0A0
i: 1761 p: 0134A180
i: 1762 p: 0134A1F0
i: 1763 p: 0134A228
i: 1764 p: 0134A260
i: 1765 p: 0134A378
i: 1766 p: 0134A7D8
v3dCalculation:: calculation_thread_009 () ends.
send_main
main ends.

---