summaryrefslogtreecommitdiff
path: root/cpan/ExtUtils-Constant/lib/ExtUtils/Constant.pm
Commit message (Collapse)AuthorAgeFilesLines
* Bump version to 0.25.Nicholas Clark2018-04-181-1/+1
| | | | | This release contains only the 1 byte fix for perl RT #132974 The Changes file is still incomplete (see cpan RT #122854)
* ExtUtils::Constant fix "panic: failed to extend arg stack"Daniel Dragan2018-04-181-1/+1
| | | | | | | | | | | | | | "$XS_Constant{$type}" is almost always a 2nd PUSH on stack, but EU::C only extended by 1, not 2. This mistake didn't become visible until the panic assert was added 5.27.2 panic: XSUB Compress::Raw::Bzip2::constant (Bzip2.c) failed to extend arg stack: base=1b13010, sp=1b13020, hwm=1b13018 Numbers in message are from my 64bit perl, so 0x1b13020-0x1b13018=0x8 which is one 64 bit pointer stack slot, which is exactly the mistake that this patch fixes in EU::C. See RT ticket associated with this commit for details.
* Bump version to 0.24_50.Nicholas Clark2018-04-181-1/+1
|
* Bump ExtUtils::Constant version to 0.24.Nicholas Clark2017-08-081-1/+1
| | | | | | | The Changes file is still horriby out of date, and the trickier-to-fix (or test) bugs remain open in RT, but it seems better to get a release out with the fixed bugs than delay it further whilst figuring out the cleanest way to fix the open bugs. The perfect is the enemy of the good.
* EU::Constant: avoid 'uninit' warningDavid Mitchell2017-08-081-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The code generated by ExtUtils::Constant can look something like: static int constant (..., IV *iv_return) { switch (...) { case ...: *iv_return = ...; return PERL_constant_ISIV; ... } } { int type; IV iv; type = constant(..., &iv); switch (type) { case PERL_constant_ISIV: PUSHi(iv); ... } } and the compiler isn't clever enough to realise that the value of iv is only used in the code path where its been set. So initialise it to zero to shut gcc up. Ditto nv and pv.
* Minor refactor of ExtUtils::Constant::ProxySubs.Nicholas Clark2010-10-221-1/+3
| | | | | | Use a lexical in place of repeated lc()'s in WriteConstants. Require ExtUtils::Constant::ProxySubs early, to avoid leaving empty files if it fails for any reason.
* Add option croak_on_error to PROXYSUBS, to directly croak() the error message.Nicholas Clark2010-10-211-1/+1
| | | | | | | This is only useful with the code that generates Proxy Constant Subroutines, as this adds all known constants to the symbol table at compile time, meaning that the only calls to AUTOLOAD will be to load constants not available on this platform, or for invalid constant names.
* Move ExtUtils::Constant from ext/ to cpan/Nicholas Clark2009-10-021-0/+565