26

Re: Transmission under the link

ptr128 wrote:

Depends on the compiler and from a platform

And with Java was so )

27

Re: Transmission under the link

.  wrote:

it is passed...
And with Java was so )

outofmemory and any headache))

28

Re: Transmission under the link

wrote:

it is passed...
outofmemory and any headache))

Well you
Before outofmemory the patient still long enough fights in convulsions causing GC smile)))

29

Re: Transmission under the link

ptr128 wrote:

it would be possible not to encode at all, and to write down explicitly:

And here a trick with union in With ++ it already UB and thin ice.

30

Re: Transmission under the link

.  wrote:

it is passed...
And with Java was so )

Well on a C ++ in protected mode generally it is possible to catch simply exception in checkout function through try - catch. Select an array in a stack, the size in a tested store, and try to write down something in its last element.

31

Re: Transmission under the link

Dimitry Sibiryakov wrote:

it is passed...
And here a trick with union in With ++ it already UB and thin ice.

As soon as we cause function, transferring it the pointer, but without specifying the size of the buffer is already thin ice. That is, it was initially directed by the HARDWARE task)

32

Re: Transmission under the link

ptr128 wrote:

it is passed...
As soon as we cause function, transferring it the pointer, but without specifying the size of the buffer is already thin ice. That is, it was initially directed by the HARDWARE task)

I am sorry
Api mine  also accepts also the size of the buffer
Simply I did not specify it in the problem description
The size always 16 byte