IT. Expert System.

Direct Known Subclasses:

Allocation, Element, FileA3D, Font, Mesh, Path, Program, ProgramRaster, ProgramStore, Sampler, Script, Script.FieldID, Script.KernelID, ScriptGroup, Type

public class BaseObj
extends Object

• Method Summary

  Methods

  Modifier and Type	Method and Description
  void	destroy() destroy disconnects the object from the native object effectively rendering this java object dead.
  boolean	equals(Object obj) Compare the current BaseObj with another BaseObj for equality.
  protected void	finalize() Invoked when the garbage collector has detected that this instance is no longer reachable.
  String	getName()
  int	hashCode() Calculates the hash code value for a BaseObj.
  void	setName(String name) setName assigns a name to an object.

  • Methods inherited from class java.lang.Object

    clone, getClass, notify, notifyAll, toString, wait, wait, wait

• Method Detail

  • setName

    public void setName(String name)

    setName assigns a name to an object. This object can later be looked up by this name. This name will also be retained if the object is written to an A3D file.

    Parameters:

    name - The name to assign to the object.

  • getName

    public String getName()

    Returns:

    name of the renderscript object

  • 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

  • destroy

    public void destroy()

    destroy disconnects the object from the native object effectively rendering this java object dead. The primary use is to force immediate cleanup of resources when it is believed the GC will not respond quickly enough.

  • hashCode

    public int hashCode()

    Calculates the hash code value for a BaseObj.

    Overrides:

    hashCode in class Object

    Returns:

    int

    See Also:

    Object.equals(java.lang.Object)

  • equals

    public boolean equals(Object obj)

    Compare the current BaseObj with another BaseObj for equality.

    Overrides:

    equals in class Object

    Parameters:

    obj - The object to check equality with.

    Returns:

    boolean

    See Also:

    Object.hashCode()