> Amen. plperlNG was always intended as a replacement.
>
> In fact, one of the reasons I'm a bit sad about us rushing to feature
> freeze on 1 June is that Joshua and I had hoped to get a greatly beefed
> up plperl ready in time for 7.5, but I don't think we can make June 1.
I don't think we will make it either. June 15th maybe.
Sincerely,
Joshua D. Drake