Lines Matching refs:objects
92 code should distinguish "small" objects (kept in near data space) from
286 The control modules are objects. A considerable amount of flexibility can
324 The objects shown above are:
373 In addition to the above objects, the compression library includes these
374 objects:
399 The error handler, destination manager, and progress monitor objects are
400 defined as separate objects in order to simplify application-specific
403 objects. The object interfaces for these objects are therefore treated as
404 part of the application interface of the library, whereas the other objects
424 As before, this diagram also represents typical control flow. The objects
493 In addition to the above objects, the decompression library includes these
494 objects:
746 In all cases, allocated objects are tied to a particular compression or
750 The memory manager does not provide explicit deallocation of objects.
751 Instead, objects are created in "pools" of free storage, and a whole pool
754 The pools can be regarded as lifetime identifiers for objects. Two
767 1. "Small" objects. Typically these require no more than 10K-20K total.
768 2. "Large" objects. These may require tens to hundreds of K depending on
769 image size. Semantically they behave the same as small objects, but we
771 * On MS-DOS machines, large objects are referenced by FAR pointers,
772 small objects by NEAR pointers.
773 * Pool allocation heuristics may differ for large and small objects.
774 Note that individual "large" objects cannot exceed the size allowed by
776 3. "Virtual" objects. These are large 2-D arrays of JSAMPLEs or JBLOCKs
783 objects for the data proper and small objects for the row pointers. For
791 multiple passes through the image.) We also expect that only "small" objects
805 realize routine must allow for space occupied by non-virtual large objects.
806 (We don't bother to factor in the space needed for small objects, on the
813 2. All "large" objects (including JSAMPARRAYs and JBLOCKARRAYs) must also be
818 Small objects of any lifespan may be allocated at any time. We expect that
819 the total space used for small objects will be small enough to be negligible
878 It may be necessary to ensure that backing store objects are explicitly