Lines Matching full:manager
389 * Data destination manager: writes the output JPEG datastream to its final
390 destination (e.g., a file). The destination manager supplied with the
392 surrounding application may provide its own destination manager.
394 * Memory manager: allocates and releases memory, controls virtual arrays
405 The error handler, destination manager, and progress monitor objects are
413 The error handler and memory manager are shared by JPEG compression and
509 * Data source manager: supplies the input JPEG datastream. The source
510 manager supplied with the library knows how to read from a stdio stream;
512 manager.
514 * Memory manager: same as for compression library.
520 As with compression, the data source manager, error handler, and progress
745 *** Memory manager services ***
747 The JPEG library's memory manager controls allocation and deallocation of
750 memory manager serves both compression and decompression operations.
756 The memory manager does not provide explicit deallocation of objects.
772 The memory manager deals with three kinds of object:
784 memory manager provides stripwise access to these arrays. On machines
790 convenience and speed, the memory manager provides single routines to create
799 the memory manager.
804 swapping would be very wasteful.) The memory manager will adjust the height
806 to do this in a reasonably optimal fashion, the manager needs to allocate all
816 with the memory manager:
850 *** Memory manager internal structure ***
853 memory manager into two parts. There is a reasonably system-independent
893 The IJG distribution includes several memory manager back end implementations.
