Sam Ruby <[EMAIL PROTECTED]> wrote: > I just spent some time debugging a problem which turned out to be due to > the "set" operator not doing what I expected (i.e., calling pmc_set). > In retrospect, what set id doing is perfectly defensible, but "setref", > as implemented by PerlScalar, remains counter intuitive, at least to me:
Yep. The C<setref> opcode is intended to set a reference inside a reference type, like Ref or SharedRef. The implementation of perlscalar's setref is the old "assign the RHS value" behavior. We have to cleanup classes. > - Sam Ruby leo
