Index of /hlt/src/hlt-stale/osf/apps/v3

Redesign of OSF from V2 to V3

• The V3 source documentation is in directory ./apps/v3/docs/OsfV3Doc/000StartHere.html

• Links to the V3 sources are listed in file ./doc/000StartHere.html

• Following are the essential changes modifications that version v3 makes to version v2.

  • In the package hlt.osf.util, a new class is introduced called Decoded as the type of objects that gather all information corresponding to decoding a Bitcode) object.

  • Such a Decoded object is systematically associated to every Bitcode object. It gathers the following information:

    • a Sort object (if the code corresponds to one, null otherwise);

    • the set of sorts (a java.util.HashSet of Sort objects) that have a code immediately greater than its code (i.e., the code's lub's);

    • the set of sorts that have a code immediately lower than its code (i.e., the code's glb's).

    It is also the cache-repository of its code's ancestors and descendants, all of which are computed only if/when accessed, and then cached as appropriate attributes of the Decoded object.

  • A unique new Decoded(Sort sort) is created and associated with each sort at Taxonomy initialization time (more precisely, right after sort encoding when committing its corresponding sort).

  • The above change entails a major deep restructuring and redefinition of some of most important classes in the hlt.osf package. In particular:

    • exec/Taxonomy.java;

    • util/BitCode.java; and,

    • base/Sort.java.

    Whereas in v2 this last class contained and cached computation of ancestors and descendants, this is no longer the case in v3 where all such computation and caching are now done through the Decoded class.

    All Sort objects now have a unique associated Decoded object where all such relevant information is computed and cached.

    This implies rewriting much of the Bitcode class as well.

  • The introduction of the Decoded class implies many changes to be made in all these classes (and a few others that are affected). The most important are:
    • the _codeCache table in exec/Context.java associates Bitcode objects no longer to Sort objects but to Decoded objects; and,

    • All computation and caching of parents and ancestors, children and descendants is no longer done in base/Sort.java but in util/Decoded.java.