Hi all -
I don't know if this is the right list for this email, but it seemed
like the most relevant one.
Currently, we're using perl-5.6.1 and are having problems with memory
leaks - thanks to reference counting.
I'm just curious how stable parrot's GC engine is, and how much effort
it'd take t
Time to finish this one and ensconce the API into the embedding interface.
We dynamically load libraries. Whee! Yay, us. We need a set of
semantics defined and an API to go with them so we can meaningfully
and reliably work with them.
So, to start, here are the semantics I think we're going to n
# New Ticket Created by Mattia Barbon
# Please include the string: [perl #31379]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31379 >
Hello,
this patch implements Parrot_call_method (with test).
It also adds a note t
On Aug-27, Leopold Toetsch wrote:
> Steve Fink wrote:
> >On Aug-26, Leopold Toetsch wrote:
>
> >>.sub @regex_at_foo_imc_line_4711 # e.g.
>
> >Yes, this illustrates what I was really getting at. My compiler can
> >certainly take a subroutine name (or file and line number, or whatever)
> >to use t
On Aug-26, Leopold Toetsch wrote:
> Steve Fink wrote:
>
> >I can store some global counter that makes it generate different sub
> >names each time, but that seems a bit hackish given that I don't really
> >want the subroutine to be globally visible anyway; I'm just using one so
> >that I can use P
