libcore.util

Class ZoneInfoDB.TzDataDefault

java.lang.Object

libcore.util.ZoneInfoDB.TzData

libcore.util.ZoneInfoDB.TzDataDefault

Enclosing class:

ZoneInfoDB

public static class ZoneInfoDB.TzDataDefault
extends ZoneInfoDB.TzData

Constructor Summary

Constructors

Constructor and Description
TzDataDefault(String... paths)

Method Summary

Modifier and Type	Method and Description
protected void	finalize() Invoked when the garbage collector has detected that this instance is no longer reachable.
String[]	getAvailableIDs()
String[]	getAvailableIDs(int rawUtcOffset)
String	getVersion()
String	getZoneTab()
boolean	hasTimeZone(String id)
ZoneInfo	makeTimeZone(String id)

Methods inherited from class libcore.util.ZoneInfoDB.TzData

getDefaultID

Methods inherited from class java.lang.Object

clone, equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

TzDataDefault

public TzDataDefault(String... paths)

Method Detail

getAvailableIDs

public String[] getAvailableIDs()

Specified by:

getAvailableIDs in class ZoneInfoDB.TzData

getAvailableIDs

public String[] getAvailableIDs(int rawUtcOffset)

Specified by:

getAvailableIDs in class ZoneInfoDB.TzData

getVersion

public String getVersion()

Specified by:

getVersion in class ZoneInfoDB.TzData

getZoneTab

public String getZoneTab()

Specified by:

getZoneTab in class ZoneInfoDB.TzData

makeTimeZone

public ZoneInfo makeTimeZone(String id)
                      throws IOException

Specified by:

makeTimeZone in class ZoneInfoDB.TzData

Throws:

IOException

hasTimeZone

public boolean hasTimeZone(String id)
                    throws IOException

Throws:

IOException

finalize

protected void finalize()
                 throws Throwable

Description copied from class: Object

Invoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.

Note that objects that override finalize are significantly more expensive than objects that don't. Finalizers may be run a long time after the object is no longer reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup. Note also that finalizers are run on a single VM-wide finalizer thread, so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary for a class that has a native peer and needs to call a native method to destroy that peer. Even then, it's better to provide an explicit close method (and implement Closeable), and insist that callers manually dispose of instances. This works well for something like files, but less well for something like a BigInteger where typical calling code would have to deal with lots of temporaries. Unfortunately, code that creates lots of temporaries is the worst kind of code from the point of view of the single finalizer thread.

If you must use finalizers, consider at least providing your own ReferenceQueue and having your own thread process that queue.

Unlike constructors, finalizers are not automatically chained. You are responsible for calling super.finalize() yourself.

Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.

Overrides:

finalize in class Object

Throws:

Throwable