Re: Encode::FB_CROAK eating up strings?

[Anonymous Monk]

Encode::FB_CROAK | Encode::LEAVE_SRC is the incantation you want.

I tried to look in the docs for Encode but to no avail

Yes, it's easy to miss, but it's documented: 'If the "Encode::LEAVE_SRC" bit is not set but CHECK is set, then the source string to encode() or decode() will be overwritten in place. If you're not interested in this, then bitwise-OR it with the bitmask.'

[polettix]

Thanks for pointing out.

I personally think that the docs might use some clarifications directly in encode and decode to change people's expectations. I'll try to propose a doc patch where this possibility is mentioned explicitly.

Update: just sent a Pull Request at https://github.com/dankogai/p5-encode/pull/54.

Update: merged, yay!