What methods should go into a java.util.Objects class in JDK 7? (original) (raw)
Alan Bateman Alan.Bateman at Sun.COM
Mon Oct 12 14:26:44 UTC 2009
- Previous message: What methods should go into a java.util.Objects class in JDK 7?
- Next message: What methods should go into a java.util.Objects class in JDK 7?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ulf Zibis wrote:
Am 12.10.2009 15:03, Ulf Zibis schrieb:
Additionally something like Path#unlock() would be helpful, if copy/delete fails. For example see: http://diamondcs.com.au/freeutilities/fileunlocker.php Additionally see: http://ccollomb.free.fr/unlocker/ I assume this type of thing can lead to data loss and/or hard to diagnose corruption. If you are running into sharing violations then try out the file system API as the Windows provider opens files by default to allow delete access (ie: close to Unix semantics by default with provider specific options to control the DOS sharing mode if you really want). The only case where we still have a problem is memory-mapped files. Changing the long standing behavior of the java.io classes is another matter as that would likely break existing applications that rely on the current/long standing behavior.
-Alan.
- Previous message: What methods should go into a java.util.Objects class in JDK 7?
- Next message: What methods should go into a java.util.Objects class in JDK 7?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]