Gundam Wing: Du oMaxwell:

That result is more interesting.
We can use a pointer allocation as a param from the sublootin as a returnable value.

*

    lootin:
        a pointer <- allocation
        sublootin a pointer:
            a pointer <- allocation

Gundam 00: "Tieria Erde"

Realloc is a function also.
That way is not wrong enough because that is the proofment and we can change the size of allocation from the address known as a value like a pointer in C.
In C, as a pointer is valuable and becoming to the sublootin.
At the least, in the function and inside, you can change string buffer allocation by the use of realloc of functions.

*

*
    lootin:
        a pointer <- allocation
        sublootin a pointer:
            a pointer <- reallocation
 

*

Gundam 00: Tieria Erde

Their thought is all from functions in windows-api.
So, we have to use the functions for drawing, which means you use the old refreshed functions and their remained still.
New and old functions should be separated for the refreshment.

*

-	-	flashing api	double buffered	-	-
	Draw a pixel		SetPixel
	Draw a line
	Draw fonts
	Draw a shape

*

Gundum Wing: Duo Maxwell:

No doubt and no matter how and otherwise:
Pictured buffer should be prepared in 2D Canvas in any way no matter how they prepared the double buffer or not.
Otherwise, you lost the control and flexibility for the flash and flushing memories.

1. When you draw the picture, ...
2. When you write the font as literature, ...
3. The flashing matter is not only for the 1.
4-1. In the 2, we can create the easy font animation and proof it.
4-2. We also can draw 3 lines as axex but it was flashing and we could not feel so as font in same process like 4-1.

*
In addition, we could write the font on the memorized buffer not attached from the basic process if we prepared the double buffer.

[1]
[2]
[3]
[4]

Gundam Wing: Duo Maxwell:

Memorized question is ...
The do not heart the memorized process, and so I like it but ...

1. We usually use the memorized buffer for the process.
2. Touch of the memorization is relative to their size, anyway, not absolute enough.
3. In Code of C, "int" is 4, and "double" is 8 bytes as allocation size.
4. They create the stack is first and use the structure of data.

*
[1]
[2]
[3]
[4]