26

Re: Why at an output from function?

The functions, which select the buffer not always are efficient.
For example c# cannot read this buffer. Here recently  to fasten library with  the interface to to a sharp - access to protected  storages at attempt to read such line. And if to transfer the pointer to the buffer and its size  - it is possible to fill all.

27

Re: Why at an output from function?

alexy_black wrote:

for example c# cannot read this buffer

It not so, can easily and easy. Another matter - with clearing of this buffer - it is necessary to know precisely a selection method (GlobalAlloc, SysAllocString, CoTaskMemAlloc and ), if malloc - chances naturally any

28

Re: Why at an output from function?

Isokerf;
Yes,  - it is unambiguous.
It is just necessary to know how to cook.
Besides, time library it is not connected to problems of C Run in any way.

29

Re: Why at an output from function?

I did not, I am not engaged in such hogwash.
Function  const char*, and inside it was c_str () from a standard line which did not disappear after  from function. The code worked normally, when I it from  sinkers. And here  did not master - at once fell at reversal attempt there. Therefore I made function which  the pointer and the size of the buffer and filled it.

30

Re: Why at an output from function?

alexy_black wrote:

  I did not, I am not engaged in such hogwash

In documentation reading - too be not engaged?