On Sun, 02 Mar 2008, Sisyphus wrote:
> Thanks for the explanation.
> It seems that the goal posts were moved with the release of perl 5.10 - a
> number of functions that were private in perl 5.8 are now apparently public.
>
> For example, Data-Alias-1.07 fails to build on perl 5.8 (Windows and AIX
> only) because it tries to access the private perl API. The make process
> terminates as follows:
[...]
> But on Win32 perl 5.10, the exact same source builds and tests fine.
>
> Were all of those 5.8 private functions (specified above) made public on
> perl 5.10 just to accommodate Data::Alias ? Or are there other forces at
> work here ?
Yes, they were made available for Data::Alias. They are still not supposed
to be part of the public API, but only to core modules bundled with Perl,
but of course any module can cheat and #define PERL_EXT anyways. You just
won't get much sympathy if your module breaks due to core changes if you
do that...
I think the plan was to make Data::Alias a core module, eventually, because
it is pretty tightly involved with the Perl internals.
Anyways, the 2 changes I could find that explicitly make symbols available
for Data::Alias are:
http://public.activestate.com/cgi-bin/perlbrowse/p/30716
http://public.activestate.com/cgi-bin/perlbrowse/p/31133
You'll see that the APIs are marked 'EX' if embed.fnc and not 'A'. That
means they are still not considered part of the public API, and they may
change from release to release.
Cheers,
-Jan
_______________________________________________
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
