> There is a fundemental issue on how values are passed between
> threads. Does the value leave one thread and enter the other or are
> they shared.
> The idea tossed around -internals was that a value that crosses a thread
> boundary would have a wrapper/proxy attached to handle the mediation.
| Transactions are obviously going to be expensive and complicated,
| which
| is why I suggested implementing them outside the core:
[...]
| That's not quite sufficient for full transactions either. We
| should also allow
| user code to replace the assignment op in the virtual machi
This message on perl5-porters brought an idea to mind:
Paul Marquess <[EMAIL PROTECTED]> writes:
> From: Marc Lehmann [mailto:[EMAIL PROTECTED]]
>> Actually, the perl binary links against waay too many libraries. As a
>> rule of thumb, the perl binary is linked against all libraries any
>> exte
