🚀 go-pugleaf

I've been learning to use the WIN32 API function
ReadFile() to read in text to an edit control using
the SetWindowText() function.

During this process I have seen that Petzold
appends null characters to the buffer that receives
data before sending the text to an edit control
(in his Poppad3 example, Chapter 11).  But, I've
noticed if I skip this step and compile Poppad3,
the result is the same. The buffer is still
used by SetWindowText to fill the edit control
whether I append a null character or not.

I don't fully understand the buffer returned by
ReadFile(), and have searched without luck for a
detailed description on MSDN and Google. I assume it
is just a pointer to a block of memory I allocate with
the value I get from GetFileSize(), so it should not be
considered a string by SetWindowText().

Is it safe to assume that ReadFile() never returns a
null character in the buffer after a read? Or, does
it place one there after a read? If anyone can point
me to a discussion of the buffer used by ReadFile(),
it would be most helpful.

Thanks,

Bill