Lines Matching refs:objects
100 code should distinguish "small" objects (kept in near data space) from
294 The control modules are objects. A considerable amount of flexibility can
332 The objects shown above are:
380 In addition to the above objects, the compression library includes these
381 objects:
405 The error handler, destination manager, and progress monitor objects are
406 defined as separate objects in order to simplify application-specific
409 objects. The object interfaces for these objects are therefore treated as
410 part of the application interface of the library, whereas the other objects
430 As before, this diagram also represents typical control flow. The objects
499 In addition to the above objects, the decompression library includes these
500 objects:
752 In all cases, allocated objects are tied to a particular compression or
756 The memory manager does not provide explicit deallocation of objects.
757 Instead, objects are created in "pools" of free storage, and a whole pool
760 The pools can be regarded as lifetime identifiers for objects. Two
773 1. "Small" objects. Typically these require no more than 10K-20K total.
774 2. "Large" objects. These may require tens to hundreds of K depending on
775 image size. Semantically they behave the same as small objects, but we
777 * On MS-DOS machines, large objects are referenced by FAR pointers,
778 small objects by NEAR pointers.
779 * Pool allocation heuristics may differ for large and small objects.
780 Note that individual "large" objects cannot exceed the size allowed by
782 3. "Virtual" objects. These are large 2-D arrays of JSAMPLEs or JBLOCKs
789 objects for the data proper and small objects for the row pointers. For
797 multiple passes through the image.) We also expect that only "small" objects
811 realize routine must allow for space occupied by non-virtual large objects.
812 (We don't bother to factor in the space needed for small objects, on the
819 2. All "large" objects (including JSAMPARRAYs and JBLOCKARRAYs) must also be
824 Small objects of any lifespan may be allocated at any time. We expect that
825 the total space used for small objects will be small enough to be negligible
884 It may be necessary to ensure that backing store objects are explicitly