[perl #129058] Perl_do_vop: resulting string isn't alwaysnull-terminated

Upon further review, the AND case is deliberately different than the OR and XOR cases. I can tell because when I applied my patch that has the AND case just jump to mop_up_utf, the test suite failed a lot in t/op/bop.t. So instead I'll be a bit less heavy-handed and just pull in the line that NUL-terminates the string. This passes all tests (woo!).

My question - there was a recent discussion about whether perl strings could be assumed to be null-terminated. The outcome, as I understand it, was that perl strings would usually be null-terminated, but XS code could produce SVs with unterminated strings. So while this patch fixes one issue by null-terminating this particular string, a question: Is it safe, in the general case, for Perl_my_atof2() to use strlen? If not, there are surely more similar bugs hiding out. (That discussion was in RT #128170)

-- 
Respectfully,
Dan Collins

---
via perlbug:  queue: perl5 status: new
https://rt.perl.org/Ticket/Display.html?id=129058

• [perl #129058] Perl_do_vop: resulting string isn't alwaysnull-terminated by Dan Collins via RT
• Re: [perl #129058] Perl_do_vop: resulting string isn't alwaysnull-terminated by Zefram
• [perl #129058] Perl_do_vop: resulting string isn't alwaysnull-terminated by Dan Collins