Mattia Barbon <[EMAIL PROTECTED]> wrote:
> I am not sure about this patch. It splits part of Parrot_load_lib
> into a Parrot_init_lib(Interp, load_func_ptr, init_func_ptr)
So its applied finally. Thanks,
leo
I would be very greatful if you worked on this. =-)
This came up a few months ago with Tcl - there are several inter-related PMC, just
like the Perl* PMCs (which only work because they are NOT dynpmcs...) - you cannot
compile them individually, you must do them all at once. I tabled working with
[got a failure, sorry if this is a duplicate]
On 15 Aug 2004 10:11:11 - Leopold Toetsch via RT <[EMAIL PROTECTED]> wrote:
> Mattia Barbon <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> > I am not sure about this patch. It splits part of Parrot_load_lib
> > into a Parrot_init_lib(Interp, load_fu
Mattia Barbon <[EMAIL PROTECTED]> wrote:
> Hello,
> I am not sure about this patch. It splits part of Parrot_load_lib
> into a Parrot_init_lib(Interp, load_func_ptr, init_func_ptr)
> where load/init_func_ptr are pointers to the function loadlib calls. The
> objective is allowing dynamic PMCs lin
# New Ticket Created by Mattia Barbon
# Please include the string: [perl #31114]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31114 >
Hello,
I am not sure about this patch. It splits part of Parrot_load_lib
into a Pa
