Examples of EObject

erjang.EObject

The base class for representing Erlang values. This class embodies in particular (the base of) the following concerns: - Dynamic value kind testing; - Erlang value ordering (incl. "compare-same") and "exact equality" (as used in matching). - The unary and binary operators built into the Erlang language Furthermore, the class contains helper methods concerned with: - building and flattening of lists; - counting up and down, and integer zero-testing. (TODO: consider these) Regarding EObjects and collections: Erjang will need to form both hash tables and ordered collections of EObjects. For hashing purposes, EObject implements equals() and hashCode(). While EObjects have an ordering (the value ordering defined by Erlang), it is not total: an integer and its floating-point equivalent are considered equivalent as far as the ordering is concerned, though not by equals(). EObject therefore intentionally does not implement Comparable; instead, use the explicit comparator EObject.ERLANG_ORDERING. (This is also the reason that its comparison method is called erlangCompareTo() rather than plain compareTo().)

org.eclipse.emf.ecore.EObject

A representation of the model object 'EObject'.

EObject is the root of all modeled objects so all the method names start with "e" to distinguish the EMF methods from the client methods. It provides support for the behaviors and features common to all modeled objects:

Content

{@link #eResource()}
{@link #eContainer}
{@link #eContainingFeature}
{@link #eContainmentFeature}
{@link #eContents}
{@link #eAllContents()}
{@link #eCrossReferences}

Reflection

{@link #eClass}
{@link #eGet(EStructuralFeature)}
{@link #eGet(EStructuralFeature,boolean)}
{@link #eSet(EStructuralFeature,Object)}
{@link #eIsSet(EStructuralFeature)}
{@link #eUnset(EStructuralFeature)}

Serialization

{@link #eIsProxy}

It is a full participant of the common notification framework: {@link org.eclipse.emf.common.notify}. Any EObject is assumed to also implement {@link InternalEObject}, which provides lower-level access that is not necessarily suitable for general consumption but is required for maintaining the EMF support mechanisms. Implementations of EObject should extend {@link org.eclipse.emf.ecore.impl.BasicEObjectImpl BasicEObjectImpl} or one of its derived classes because methods can and will be added to this API. The framework also assumes that implementations will not specialize {@link #equals(Object)} (nor {@link #hashCode()}) so that "==" can be always used for equality testing; {@link org.eclipse.emf.ecore.util.EcoreUtil#equals(EObject,EObject) EcoreUtil.equals} should be used for doing structural equality testing.

@extends Notifier @see org.eclipse.emf.ecore.EcorePackage#getEObject() @model @generated

   */
  protected void expect(CharSequence input, int errorCount, int warningCount) {
    List<String> tokens = null;
    //Assert::assertEquals('warnings ' + resource.warnings, 0, resource.warnings.size)
    //Assert::assertEquals('errors ' + resource.errors, 0, resource.errors.size)
    EObject parseResult = null;
    EList<Diagnostic> errors = null;
    EList<Diagnostic> warnings = null;
    try {
      Lexer lexer = new Lexer(input);
      tokens = lexer.tokenizeToStrings();

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of EObject

Examples of org.eclipse.emf.ecore.EObject