Page History

...

1. save one slot per feature structure - instead of a casImpl ref and a typeImpl ref, there was just one ref to the _Type instance, which in turn, and these two refs

2. provided a place for the low level accessors

   .

It's unclear if anyone is using the low level accessors.  These may be retained, but moved to the main xxx classes.

1. ; these are accessors that take the "address" (now "id") of the FS as the way to designate which FS is being used.  There are 2 varieties of these low level accessors - those implemented in the CASImpl, and those implemented in the JCAS _Type classes.  The latter has methods like "myFeatureStructure.setXXX(address, value)".  Clearly, since these are instance methods on some FeatureStructure, there already exists a "handle" to that FS, making the use of the address superfluous.  

It's unlikely anyone is using the low level JCas-style accessors and they are no longer part of the API in V3For the non-JCas style of Java cover classes (FeatureStructureImplC) these did not implement a _Type instance, and had as a consequence both a casImpl ref and a typeimpl ref.

JCas Class generation

JCas cover classes now come in single classes, rather than in pairs.  These classes are either built-in or are generated; built-in ones cannot be generatedhas a ref to the CAS view.  A single class definition might be used for multiple type systems; a single definition is used for all the built in types.  Each JCas class extends

...