It's not only in PHP, I guess the author meant some further pattern recognition and code optimization thereby however misleading it might be at some point.

Hahahhahahahahahahhahahahahahahhahhahaa

ez

Thank you... i wasnt asking for "xor" actualy... i didnt know the operator "^" :D

Could someone explain that?

Issue with the PHP tests:

These incorrectly replace multiple consecutive input or output characters (, & .) with just a single putchar / getchar call.

This is incorrect, as while reading multiple bytes from input would only store the last, it would still consume multiple bytes.

Same goes for the output: the written character would be the same each time, but it would still be written twice.

(The interpreter in the tests would print Helo, World!, with just a single 'l', for example).

I could get my solution to pass by implementing the same error, but that is obviously not right.

Edit: Just noticed hotdonkey already reported this 9 months ago...

I thought of this when I looked at kyu level again after having a timeout error. No way you need to use algos for this level.

timeout error + 8 kyu = there's a simple brutforce

For the C translation, the tests expect us to return a newly-allocated character string, but never frees it. I know it doesn't free it now because the initial solution returns a statically allocated string instead and doesn't break the allocator.
A change to the function's interface or the initial solution would allow the tests to free the returned string instead of wasting that memory.

.

The tip for C: more memory,very more

completely changes the output? i dont even know how it gets the output its getting, i even tried changing compiler to match theres, and it outputs the correct answer

\n

(Thanks!)

ummmmm Expected: equal to "*p += 4;
"
Actual: "*p += 4;"