develooper Front page | perl.perl5.porters | Postings from April 2016

Re: Inconsistencies in memory size types

Thread Previous | Thread Next
From:
H.Merijn Brand
Date:
April 6, 2016 19:27
Subject:
Re: Inconsistencies in memory size types
Message ID:
20160406212624.7fb90e4a@pc09.procura.nl
On Wed, 06 Apr 2016 11:08:33 +0100, ilmari@ilmari.org (Dagfinn Ilmari
Mannsåker) wrote:

> > I don't think there are issues anymore.  Unfortunately, XS code likely
> > uses a mix of Size_t, MEM_SIZE, and STRLEN, so I'm not sure there's
> > much you can actually do.  
> 
> This is why my patch makes Size_t, MEM_SIZE and STRLEN available #ifndef
> PERL_CORE.  On second though, though, standardising on Size_t and
> SSize_t will make things easier for upstream-blead dual-life modules
> (unless they all use Devel::PPPort and we add the defines there).

Which is what I wanted to suggest. Make the core cleaner and have all
backward compat available in Devel::PPPort should only cause a *little*
extra effort on those XS modules that do not use it correct. It is
unlikely to affect end users and cpan clients

-- 
H.Merijn Brand  http://tux.nl   Perl Monger  http://amsterdam.pm.org/
using perl5.00307 .. 5.23   porting perl5 on HP-UX, AIX, and openSUSE
http://mirrors.develooper.com/hpux/        http://www.test-smoke.org/
http://qa.perl.org   http://www.goldmark.org/jeff/stupid-disclaimers/

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