kdu_tile::close

Although not strictly necessary, it is a good idea to call this function once you have finished reading from or writing to a tile.

Once closed, future attempts to access the same tile via the kdu_codestream::open_tile function will generate an error, except in the event that the codestream was created (see kdu_codestream::create) for interchange (i.e., with neither a compressed data source nor a compressed data target) or it was created for input and configured as persistent (see the kdu_codestream::set_persistent function).

With non-persistent input codestreams, the system is free to discard all internal storage associated with a closed tile at its earliest convenience.

For interchange and persistent input codestreams, all open tiles must be closed before the appearance can be modified by kdu_codestream::change_appearance or kdu_codestream::apply_input_restrictions.