zzip_open, zzip_open_ext_io, zzip_open_shared_io —
zzip_open function will
open(2) a real/zipped file
It has some magic functionality builtin - it will first try to open the given filename as a normal file. If it does not exist, the given path to the filename (if any) is split into its directory-part and the file-part. A ".zip" extension is then added to the directory-part to create the name of a zip-archive. That zip-archive (if it exists) is being searched for the file-part, and if found a zzip-handle is returned.
Note that if the file is found in the normal fs-directory the
returned structure is mostly empty and the
zzip_read call will
use the libc
read to obtain data. Otherwise a
is performed and any error mapped to
There was a possibility to transfer zziplib-specific openmodes
through o_flags but you should please not use them anymore and
zzip_open_ext_io to submit them down. The
is shallow in that it just extracts the zzipflags and calls
zzip_open_ext_io(filename, o_flags, zzipflags|0664, 0, 0)
you must stop using this extra functionality (not well known anyway) since zzip_open might be later usable to open files for writing in which case the _EXTRAFLAGS will get in conflict.
zzip_open_ext_io function uses explicit ext and io instead of the internal
defaults, setting them to zero is equivalent to
note that the two flag types have been split into an o_flags (for fcntl-like openflags) and o_modes where the latter shall carry the zzip_flags and possibly accessmodes for unix filesystems. Since this version of zziplib can not write zipfiles, it is not yet used for anything else than zzip-specific modeflags.
zzip_open_shared_io function takes an extra stream argument - if a handle has been
then ext/io can be left null and the new stream handle will pick up
the ext/io. This should be used only in specific environment however
zzip_file_real does not store any ext-sequence.
The benefit for the
zzip_open_shared_io function comes in when the old file handle
was openened from a file within a zip archive. When the new file
is in the same zip archive then the internal zzip_dir structures
will be shared. It is even quicker, as no check needs to be done
anymore trying to guess the zip archive place in the filesystem,
here we just check whether the zip archive's filepath is a prefix
part of the filename to be opened.
Note that the
zzip_open_shared_io function is also used by
will unshare the old handle, thereby possibly closing the handle.