It's been said before, but I do think that the "Perl6" name is holding back
adoption. Too many people think of the old Perl, and have no interest in
looking at what's changed in a new version of the "same" language.
Whatever the new name ultimately becomes, changing it (perhaps timed with a
new ma
om/rakudo/rakudo .
>
> Thank you!
>
> > On 22 Jan 2018, at 01:24, David E. wrote:
> >
> > I'm not certain where to report this (ie: rakudo vs MoarVM), so I'm
> starting here.
> >
> > After some experimentation, I finally traced down a segfault I
7;ve been sick lately and I am on heavy
> antihistamines, so I could just have medicine head.
>
> Here's the document I'm drawing this guess from: https://docs.perl6.org/
> language/nativecall#Function_arguments
>
> On Jan 21, 2018, at 19:24, David E. wrote:
>
> I
I'm not certain where to report this (ie: rakudo vs MoarVM), so I'm
starting here.
After some experimentation, I finally traced down a segfault I've been
getting to a memory leak in the NativeCall interface. I'm using it to
facilitate testing of a 32-bit embedded (meaning no dynamic allocation) C