>>>>> "JT" == John Tobey <[EMAIL PROTECTED]> writes: JT> SVs are never downgraded, so no one's source and destination are JT> another's respective destination and source. Maybe the above sequence JT> isn't exactly right, but if we adhere to strict rules for lock JT> sequencing, there won't be a deadlock, right? Which brings to mind, (probably more appropriate to -language) the user needs a mechanism to handle multi-object locking, or a clean method to order his lock aquisition. <chaim> -- Chaim Frenkel Nonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183
- Re: RFC 35 / Re: perl6-internals-gc sublist John Tobey
- Re: RFC 35 / Re: perl6-internals-gc sublist Dan Sugalski
- Re: RFC 35 / Re: perl6-internals-gc sublist Ken Fox
- Re: RFC 35 / Re: perl6-internals-gc sublist John Tobey
- Re: RFC 35 / Re: perl6-internals-gc sublist John Tobey
- Re: RFC 35 / Re: perl6-internals-gc sublist Dan Sugalski
- Re: RFC 35 / Re: perl6-internals-gc sublist John Tobey
- Re: RFC 35 / Re: perl6-internals-gc sublist Ken Fox
- Re: RFC 35 / Re: perl6-internals-gc sublist Dan Sugalski
- Re: RFC 35 / Re: perl6-internals-gc sublist John Tobey
- Re: Multi-object locks (was Re: RFC 35 / Re: perl6-intern... Chaim Frenkel
- Re: Multi-object locks (was Re: RFC 35 / Re: perl6-intern... Dan Sugalski
- Re: Multi-object locks (was Re: RFC 35 / Re: perl6-inte... Chaim Frenkel
- Re: Multi-object locks (was Re: RFC 35 / Re: perl6-intern... Larry Wall
- Re: Multi-object locks (was Re: RFC 35 / Re: perl6-intern... Chaim Frenkel
- Re: RFC 35 / Re: perl6-internals-gc sublist Ken Fox
- Re: RFC 35 / Re: perl6-internals-gc sublist Nick Ing-Simmons
- Re: RFC 35 / Re: perl6-internals-gc sublist Bradley M. Kuhn
- Re: perl6-internals-gc sublist Dan Sugalski
- Re: perl6-internals-gc sublist John Tobey
- Re: perl6-internals-gc sublist Dan Sugalski