Proposal: Automatic Resource Management (original) (raw)

Peter Mount peter at retep.org.uk
Sun Mar 8 06:02:42 PDT 2009

ManagedLock sounds like a good idea as it wouldn't break existing code and could then be used for other mechanisms than concurrent Lock's.

Peter

------Original Message------ From: Stefan Schulz Sender: coin-dev-bounces at openjdk.java.net To: coin-dev at openjdk.java.net ReplyTo: schulz at e-spirit.de Subject: Re: Proposal: Automatic Resource Management Sent: Mar 8, 2009 11:19

Just a thought (although I contradict one of my earlier posts): If Locks seem important for being handled by ARM (and I think they are), why not allow a seperate Interface for ARM that results in the appropriate code? Maybe a reduced Lock-Interface (e.g. ManagableLock) only containing the methods lock() and unlock().

The main argument to me for treating Locks additionally to closable resources is to give a more complete resource management construct to developers that prevents the (to be expected) ugly solution as being discussed on this list.

Stefan

-- Peter Mount (from my BlackBerry) e: peter at retep.org.uk w: http://retep.org m: +44 (0)7838 191423 / +44 (0)7903 155887

Instant Messaging: Contact me directly via Jabber or GoogleTalk at peter at retep.org or via MSN at retep207 at hotmail.com Alternatively via my BlackBerry at 2542ABDA or via GoogleTalk: petermount at gmail.com

More information about the coin-dev mailing list