On Tue, Nov 16, 1999 at 09:33:54AM -0500, dan@sidhe.org wrote: > The following patch provides a new macro, SvLOCK, which lets XS code snag a > perl-level lock on an arbitrary SV *. If you publish a macro like this for SvLOCK then you prohibit mixing in FAKE_THREADS or continuations. Granted, the Perl_call_* API already complicates things but do we want to expand on this same messy design? State should not be kept on the C stack lightly. I think a better solution is to allow a varient of XSUBs that work more like opcodes. -- "Does `competition' have an abstract purpose?" via, but not speaking for Deutsche Bank