Sam Ruby <[EMAIL PROTECTED]> wrote:
> I note that the perlscalar code is careful about multithreading issues
> (example: "if we morph to a string, first clear str_val so that after
> changing the vtable a parallel reader doesn't get a gargabe pointer"),
> but reuses a static PMC* intret.
Lets post
I note that the perlscalar code is careful about multithreading issues
(example: "if we morph to a string, first clear str_val so that after
changing the vtable a parallel reader doesn't get a gargabe pointer"),
but reuses a static PMC* intret.
The current PerlHash PMC coerces keys to strings,
