java.lang.Object
org.gjt.sp.jedit.syntax.ASPStateInfo
- class ASPStateInfo
- extends java.lang.Object
An utility class to save some relevant infos (language and client/server side)
found in SCRIPT Tags or <%@ like Tags
- Version:
- 0.6
client
boolean client
language
java.lang.String language
modes
private static java.lang.Object[][] modes
ASPStateInfo
ASPStateInfo()
ASPStateInfo
ASPStateInfo(boolean client,
java.lang.String language)
init
void init(boolean client,
java.lang.String language)
equals
public boolean equals(java.lang.Object o)
- Description copied from class:
java.lang.Object
- Determine whether this Object is semantically equal
to another Object.
There are some fairly strict requirements on this
method which subclasses must follow:
- It must be transitive. If
a.equals(b) and
b.equals(c), then a.equals(c)
must be true as well.
- It must be symmetric.
a.equals(b) and
b.equals(a) must have the same value.
- It must be reflexive.
a.equals(a) must
always be true.
- It must be consistent. Whichever value a.equals(b)
returns on the first invocation must be the value
returned on all later invocations.
a.equals(null) must be false.
- It must be consistent with hashCode(). That is,
a.equals(b) must imply
a.hashCode() == b.hashCode().
The reverse is not true; two objects that are not
equal may have the same hashcode, but that has
the potential to harm hashing performance.
This is typically overridden to throw a java.lang.ClassCastException
if the argument is not comparable to the class performing
the comparison, but that is not a requirement. It is legal
for a.equals(b) to be true even though
a.getClass() != b.getClass(). Also, it
is typical to never cause a java.lang.NullPointerException.
In general, the Collections API (java.util) use the
equals method rather than the ==
operator to compare objects. However, java.util.IdentityHashMap
is an exception to this rule, for its own good reasons.
The default implementation returns this == o.
toASPMode
byte toASPMode()
display
void display(java.io.PrintStream o)