develooper Front page | perl.perl5.porters | Postings from March 2021

Re: Perl 7: Fix string leaks?

Thread Previous | Thread Next
From:
Yuki Kimoto
Date:
March 30, 2021 07:07
Subject:
Re: Perl 7: Fix string leaks?
Message ID:
CAExogxPWWXJnV-z_BOuNxTYK=iD+-nsd2bpGkENhg5gXTgVpHQ@mail.gmail.com
I still don't understand this problem.

Is 128-255(latin-1 and UTF-8 shared) range problem?

Ideal world is what? There is only Unicode in Perl internal?




2021年3月29日(月) 19:30 Felipe Gasper <felipe@felipegasper.com>:

>
>
> > On Mar 28, 2021, at 8:24 PM, Dan Book <grinnz@gmail.com> wrote:
> >
> > I would love if this was possible as the current behavior is certainly
> broken. However, it's also relied upon, and as you know, difficult to
> determine whether it's being relied upon incorrectly. So I cannot support
> this breakage, major version or not.
> >
> > I can only see this being feasible via a feature flag, for the moment.
>
> A feature flag/pragma would be reasonable for the built-ins. (NB:
> Sys::Binmode started as a pragma; I moved it to CPAN per suggestion.) It
> would be another “use strict”, of course: a non-default that everyone is
> supposed to use.
>
> For the typemap, though, if breaking existing distributions is
> unacceptable then some versioned syntax would be needed; i.e., XS modules
> would have to opt-in to the fix.
>
> Short of that, though, maybe xsubpp should warn if people use the default
> char * or const char * mappings.
>
> All of the above can happen with Perl 5, of course.
>
> -F

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About