PATCH/RFC: Allow passing parameters to the dynamic linker
jaleto at gmail.com
Fri Mar 19 07:48:59 UTC 2010
This looks like a great start. It would be really nice to have a test
that verifies that this works. Can you think of the simplest possible
test case that would verify that this works?
This patch is very important for Blizkost, as I understand it,
Blizkost cannot load XS-based Perl 5 modules (such as Data::Dumper)
without this functionality.
On Thu, Mar 18, 2010 at 9:22 PM, Stefan O'Rear <stefanor at cox.net> wrote:
> Hello all,
> The current Parrot interface to dlopen on UNIX systems is incomplete; it does
> not allow passing control parameters, one of which is needed for the correct
> operation of Blizkost (the Perl 5 to Parrot adaptor which I am working on for
> Rakudo *). I beleive the best place to add this functionality is in Parrot
> itself, as this avoids any duplication of the configuration logic required to
> bind to the dynamic linker portably. This patch implements a portable and
> extensible interface for Parrot extensions to pass data to the Parrot dynamic
> linking mechanism. Is this acceptable for Parrot?
> This is my first Parrot patch and so I especially welcome all feedback,
> especially as regarding the PIR-level interface.
> Thank you.
> -Stefan (sorear on #parrot)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> -----END PGP SIGNATURE-----
Jonathan "Duke" Leto
jonathan at leto.net
More information about the parrot-dev