diff options
author | Niko Tyni <ntyni@debian.org> | 2008-10-19 23:25:10 +0300 |
---|---|---|
committer | Rafael Garcia-Suarez <rgarciasuarez@gmail.com> | 2009-04-08 09:36:14 +0200 |
commit | 36d7a91d2021ad52ce172e2c75a7bc5fa07e6354 (patch) | |
tree | b9b88b8453b0ea02915f6a61207053cd87e83792 /mint/pwd.c | |
parent | 9fd5bac037f142635de54421551d6c2d35ca66ed (diff) | |
download | perl-36d7a91d2021ad52ce172e2c75a7bc5fa07e6354.tar.gz |
h2xs incorrectly treats enum values like macros
Patch and description by Rainer Weikusat, forwarded from
http://bugs.debian.org/502297 :
The h2xs program scans C headers for 'constants' either defined
as preprocessor macros or via enum and builds a sorted list of names
containing the macros and enum values found in this way. This list
is then passed to ExtUtils::Constant::WriteConstants, which generates
the corresponding const-c.inc and const-xs.inc files when perl Makefile.PL
is executed. By default, ie when just processing a constant name, this
function assumes that the name refers to a preprocessor macro and
the generated C-code in const-c.inc contains conditional compilation
directives to either return the macro value or Perl_constant_NOTDEF,
depending on the defined'ness of the macro. This causes constants
defined as enumeration values to never be available to module users,
because they are not visible to the preprocessor.
Instead of passing just a name to the WriteConstants-routine, a
hashref (members documented in ExtUtils::Constant::Base(3perl))
can be used to specify more details regarding what code
should be generated for a particular constant. For an enumeration
value, a hashref constructed as
{ name => <name of the constant>, macro => 1 }
could be used to get rid of the inappropriate preprocessor
directives.
( Another version of the same fix was also submitted by Daniel Burr in
http://bugs.debian.org/320286 )
Diffstat (limited to 'mint/pwd.c')
0 files changed, 0 insertions, 0 deletions