develooper Front page | perl.perl5.porters | Postings from August 2010

is a new exportable function considered binary compatible?

Thread Next
Craig A. Berry
August 21, 2010 16:31
is a new exportable function considered binary compatible?
Message ID:
I see that current maint-5.12 has a function that didn't exist in 5.12.1:

$ gdiff -u perl-5_12_1/proto.h maint-5_12/proto.h
--- perl-5_12_1/proto.h 2010-05-13 17:01:07 -0500
+++ maint-5_12/proto.h  2010-08-20 22:18:21 -0500
@@ -1121,6 +1121,7 @@

+PERL_CALLCONV void     Perl_init_dbargs(pTHX);
 PERL_CALLCONV void     Perl_init_debugger(pTHX);
 PERL_CALLCONV void     Perl_init_stacks(pTHX);
 PERL_CALLCONV void     Perl_init_tm(pTHX_ struct tm *ptm)

In my world this would not be considered binary compatible unless
special steps were taken to move the new symbol to the end of the
shared library.  Is this not considered a problem for most/all known
linkers expected to produce the executables and shared libraries for

Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About