+2004-05-08
+ * remove bogus zzip_file_open_ext_io from zzip.h
+ * change to use mksite.sh for documentation builds
+
2004-03-08
* add link in docs/history.htm to the new appnote.txt whitepaper
on zip file format specification.
zziplib.html
htm_FILES = zzip-index.htm zzip-zip.htm zzip-file.htm zzip-sdl-rwops.htm \
zzip-extio.htm zzip-xor.htm zzip-crypt.htm \
- zzip-api.htm zzip-parse.htm \
+ zzip-api.htm zzip-basics.htm zzip-extras.htm zzip-parse.htm \
64on32.htm future.htm configs.htm sfx-make.htm \
history.htm referentials.htm copying.htm manpages.ar
SDL = @top_srcdir@/SDL
CLEANFILES = *.pc *.omf
DISTCLEANFILES = zziplib.spec manpages.ar htmpages.ar *.html *.xml
+html_FILES = $(htm_FILES:.htm=.html) \
+ $(htm_FILES:.htm=.print.html)
+ site.html site.print.html
+
default : doc
clean-doc clean-docs : clean-unpack
- rm $(DISTCLEANFILES)
$(bins)/zzxordir.c $(bins)/zzxorcat.c \
$(bins)/zzxorcopy.c $(SDL_RWOPS)
-install-docu: $(doc_FILES) $(htm_FILES:.htm=.html) $(PACKAGE)-doc.omf
+install-docu: $(doc_FILES) site.html $(PACKAGE)-doc.omf
$(mkinstalldirs) $(DESTDIR)$(pkgdocdir)
- for i in $(htm_FILES) ; do cat $${i}l \
+ for i in $(html_FILES) ; do cat $$i \
| sed -e 's:--START-->:-- :' -e 's:<!--ENDS--: --:' \
-e "s:\\(href=\"[^/\"]*\\)[.]html\":\\1.htm\":" \
-e "s:\\(href=\"[^/\"]*\\)[.]html\#:\\1.htm\#:" \
$(INSTALL_DATA) $(PACKAGE)-doc.omf $(DESTDIR)$(pkgomfdir)/
- test ".$(DESTDIR)" != "." || scrollkeeper-update
-install-sfnet: $(doc_FILES) $(htm_FILES:.htm=.html) htmpages.ar
+install-sfnet: $(doc_FILES) site.html htmpages.ar
$(mkinstalldirs) $(DESTDIR)$(SFNETDOC)
- $(INSTALL_DATA) $(htm_FILES:.htm=.html) $(DESTDIR)$(SFNETDOC)
+ $(INSTALL_DATA) $(html_FILES) $(DESTDIR)$(SFNETDOC)
for i in $(doc_FILES) $(DOCEXAMPLES) $(changelog) $(srcdir)/README.* \
; do $(INSTALL_DATA) `test -f $$i || echo $(srcdir)/`$$i \
$(DESTDIR)$(SFNETDOC) ; done
zziplib.html
htm_FILES = zzip-index.htm zzip-zip.htm zzip-file.htm zzip-sdl-rwops.htm \
- zzip-extio.htm zzip-xor.htm zzip-api.htm zzip-parse.htm \
+ zzip-extio.htm zzip-xor.htm zzip-crypt.htm \
+ zzip-api.htm zzip-basics.htm zzip-extras.htm zzip-parse.htm \
64on32.htm future.htm configs.htm sfx-make.htm \
history.htm referentials.htm copying.htm manpages.ar
CLEANFILES = *.pc *.omf
DISTCLEANFILES = zziplib.spec manpages.ar htmpages.ar *.html *.xml
+html_FILES = $(htm_FILES:.htm=.html) \
+ $(htm_FILES:.htm=.print.html)
+
+
omfdir = ${datadir}/omf
pkgomfdir = ${omfdir}/${PACKAGE}
SFNETDIR = /groups/z/zz/zziplib/htdocs
mostlyclean-libtool pdf pdf-am ps ps-am uninstall uninstall-am \
uninstall-info-am
+ site.html site.print.html
default : doc
clean-doc clean-docs : clean-unpack
- test -s zziplib1.xml && cp zziplib1.xml zziplib.xml
test -s $@ || rm $@
-install-docu: $(doc_FILES) $(htm_FILES:.htm=.html) $(PACKAGE)-doc.omf
+install-docu: $(doc_FILES) site.html $(PACKAGE)-doc.omf
$(mkinstalldirs) $(DESTDIR)$(pkgdocdir)
- for i in $(htm_FILES) ; do cat $${i}l \
+ for i in $(html_FILES) ; do cat $$i \
| sed -e 's:--START-->:-- :' -e 's:<!--ENDS--: --:' \
-e "s:\\(href=\"[^/\"]*\\)[.]html\":\\1.htm\":" \
-e "s:\\(href=\"[^/\"]*\\)[.]html\#:\\1.htm\#:" \
$(INSTALL_DATA) $(PACKAGE)-doc.omf $(DESTDIR)$(pkgomfdir)/
- test ".$(DESTDIR)" != "." || scrollkeeper-update
-install-sfnet: $(doc_FILES) $(htm_FILES:.htm=.html) htmpages.ar
+install-sfnet: $(doc_FILES) site.html htmpages.ar
$(mkinstalldirs) $(DESTDIR)$(SFNETDOC)
- $(INSTALL_DATA) $(htm_FILES:.htm=.html) $(DESTDIR)$(SFNETDOC)
+ $(INSTALL_DATA) $(html_FILES) $(DESTDIR)$(SFNETDOC)
for i in $(doc_FILES) $(DOCEXAMPLES) $(changelog) $(srcdir)/README.* \
; do $(INSTALL_DATA) `test -f $$i || echo $(srcdir)/`$$i \
$(DESTDIR)$(SFNETDOC) ; done
<br>-<a href="zzip-file.html"> Transparently</a>
<br>-<a href="zzip-sdl-rwops.html"> SDLrwops <small>Example</small></a>
<br>-<a href="zzip-extio.html"> ext/io <small>Customization</small></a>
-<br> <a href="zzip-xor.html"> xor/io <small>Obfuscation</small></a>
-<br> <a href="zzip-crypt.html"> zip/no <small>Encryption</small></a>
-<br>=<a href="zzip-api.html">Library API</a>
-<br>-<a href="zzip-parse.html"> Parsing ZIPs</a>
+<br><><a href="zzip-xor.html"> xor/io <small>Obfuscation</small></a>
+<br><><a href="zzip-crypt.html"> zip/no <small>Encryption</small></a>
+<br>-<a href="zzip-api.html"> Library API</a>
+<br><><a href="zzip-basics.html"> basics</a></u>
+<><a href="zzip-extras.html"> extras</a></u>
+<br>=<a href="zzip-parse.html">Parsing ZIPs</a>
<br>-<a href="64on32.html"> 64on32 extras</a>
<br>-<a href="future.html"> Next To Come</a>
<br>-<a href="configs.html"> Config Helpers</a>
</p>
<!--mksite:emailfooter:guidod@gmx.de?subject=zzip:-->
+<p align="right"><small><small>
+ created with <a href="http://zziplib.sf.net/mksite">mksite.sh</a>
+</p>
+
</td><td>
</td></tr></table></body></html>
# 2. Altered source versions must be plainly marked as such, and must not
# be misrepresented as being the original software.
# 3. This notice may not be removed or altered from any source distribution.
-# $Id: mksite.sh,v 1.1 2004-05-08 17:52:52 guidod Exp $
+# $Id: mksite.sh,v 1.2 2004-05-08 19:37:52 guidod Exp $
# initialize some defaults
test ".$SITEFILE" = "." && test -f site.htm && SITEFILE=site.htm
# marks all interesting lines so they can be checked later
# with an sed anchor of <!--sect[$NN]--> (or <!--sect[$AZ]-->)
S="\\ \\;"
-Hr="<hr>"
-He="<hr><em>"
-Hs="<strong>"
-Br="<br>"
-Pr="<br>$S"
-Rr="<br><>"
-Bs="<br><small>"
-Ps="<br>$S<small>"
-Rs="<br><><small>"
-Be="<br><em>"
-Pe="<br>$S<em>"
-Re="<br><><em>"
-Eu="<u>"
-Es="<small>"
-echo "/^$Hr[-|[]*<a href=/s/^/<!--sect1-->/" > $MK.gets.tmp
-echo "/^$He[-|[]*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
-echo "/^$Hs[-|[]*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
-echo "/^$Br[*=][*=]*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
-echo "/^$Br[-|][-|]*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
-echo "/^$Br[/:][/:]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Es[/:,[]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Br[-|[]*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
-echo "/^$Bs[-|[]*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
-echo "/^$Be[-|[]*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
-echo "/^$Eu[-|[]*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
-echo "/^$Br[\\/:]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Pr[\\/:]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Rr[\\/:]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Bs[\\/:]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Ps[\\/:]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Rs[\\/:]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Be[\\/:]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Pe[\\/:]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Re[\\/:]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
-echo "/^$Es[\\/:,[]*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+HR1="<hr>"
+HR2="$S<hr>"
+HR3="<><hr>"
+HE1="<hr><em>"
+HE2="$S<hr><em>"
+HE3="<><hr><em>"
+HS1="<hr><strong>"
+HS2="$S<hr><strong>"
+HS3="<><hr><strong>"
+BR1="<br>"
+BR2="$S<br>"
+BR3="<><br>"
+BE1="<br><em>"
+BE2="$S<br><em>"
+BE3="<><br><em>"
+QE1="<em>"
+QE2="$S<em>"
+QE3="<><em>"
+BU1="<br><u>"
+BU2="$S<br><u>"
+BU3="<><br><u>"
+QU1="<u>"
+QU2="$S<u>"
+QU3="<><u>"
+BL1="<br><small>"
+BL2="$S<br><small>"
+BL3="<><br><small>"
+QL1="<small>"
+QL2="$S<small>"
+QL3="<><small>"
+QR0=""
+QR2="$S"
+QR3="<>"
+h1="[-|[]"
+h1m="$S"
+h1n="<>"
+b1="[*=]"
+b2="[-|[]"
+b3="[\\/:]"
+b3m="$S"
+b3n="<>"
+q3="[\\/:,[]"
+q3m="$S"
+q3n="<>"
+echo "/^$HR1$h1n<a href=/s/^/<!--sect1-->/" > $MK.gets.tmp
+echo "/^$HR1$h1m<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$HR1$h1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$HR2$h1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$HR3$h1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$HE1$h1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$HE2$h1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$HE3$h1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$HS1$h1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$HS2$h1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$HS3$h1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$BR1$b1$b1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$BR2$b1$b1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$BR3$b1$b1*<a href=/s/^/<!--sect1-->/" >> $MK.gets.tmp
+echo "/^$BR1$b2$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BR2$b2$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BR3$b2$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BR1$b3$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BR2$b3$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BR3$b3$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QR0$b2$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$QR2$b2$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$QR3$b2$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$QR0$b3$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QR2$b3$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QR3$b3$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QE1$q3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QE2$q3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QE3$q3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BR1$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BR2$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BR3$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BL1$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BL2$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BL3$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BE1$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BE2$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$BE3$b2*<a href=/s/^/<!--sect2-->/" >> $MK.gets.tmp
+echo "/^$QU1$b2*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QU2$b2*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QU3$b2*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BR1$b3n<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BR1$b3m<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BR1$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BR2$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BR3$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QR2$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QR3$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BL1$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BL2$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BL3$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BE1$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BE2$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$BE3$b3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QE1$q3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QE2$q3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
+echo "/^$QE3$q3*<a href=/s/^/<!--sect3-->/" >> $MK.gets.tmp
$SED -e "s/>\\[/> *[/" ./$MK.gets.tmp > $MK.puts.tmp
# the .puts.tmp variant is used to <b><a href=..></b> some hrefs which
# shall not be used otherwise for being generated - this is nice for
<!--border--> <date> 20. July 2002 </date>
-<h3> Basics </h3>
-
-<P>
- The naming schem of functions in this library follow a simple rule:
- if you see a function with a <code>zzip_</code> prefix followed by
- compact name representing otherwise a C library or posix function then
- it is a magic wrapper that can automagically handle both real
- files/directories or zip-contained files. This includes:
-</P>
-<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
- <tr><td width=50%> zzip_opendir </td><td width=50%> opendir </td></tr>
- <tr><td width=50%> zzip_readdir </td><td width=50%> readdir </td></tr>
- <tr><td width=50%> zzip_closedir </td><td width=50%> closedir </td></tr>
- <tr><td width=50%> zzip_rewinddir </td><td width=50%> rewinddir </td></tr>
- <tr><td width=50%> zzip_telldir </td><td width=50%> telldir </td></tr>
- <tr><td width=50%> zzip_seekdir </td><td width=50%> seekdir </td></tr>
-</table></td></tr></table>
-<P>
- The ZZIP_DIR handle can wrap both a real directory or a zip-file.
- Note that you can not open a virtual directory <em>within</em> a
- zip-file, the ZZIP_DIR is either a real DIR-handle of a real
- directory or the reference of ZIP-file but never a DIR-handle
- within a ZIP-file - there is no such schema of a SUB-DIR handle
- implemented in this library. A ZZIP_DIR does actually represent
- the central directory of a ZIP-file, so that each file entry in
- this ZZIP-DIR can possibly have a subpath prepended.
-</P>
-
<P>
- This form of magic has historic reasons as originally the
- magic wrappers of this library were not meant to wrap a complete
- subtree of a real file tree but only a single directory being
- wrapped with into a zip-file and placed instead. Later proposals
- and patches were coming in to support subtree wrapping by not
- only making a split between the dir-part and file-part but
- going recursivly up through all "/"-dirseparators of a filepath
- given to <code>zzip_open</code> and looking for zip-file there.
-</P>
-
-<P>
- To open a zip-file unconditionally one should be using their
- respective methods that would return a ZZIP_DIR handle being
- the representant memory instance of a ZIP-DIR, the central
- directory of a zip-file. From that ZZIP-DIR one can open a
- compressed file entry which will be returned as a ZZIP_FILE
- pointer.
-</P>
-<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
- <tr><td width=50%> zzip_dir_open </td>
- <td width=50%> open a zip-file and parse the central directory
- to a memory shadow</td></tr>
- <tr><td width=50%> zzip_dir_close </td>
- <td width=50%> close a zip-file and free the memory shadow</td></tr>
- <tr><td width=50%> zzip_dir_fdopen </td>
- <td width=50%> aquire the given posix-file and try to parse it
- as a zip-file.</td></tr>
- <tr><td width=50%> zzip_dir_read </td>
- <td width=50%> return the next info entry of a zip-file's central
- directory - this would include a possible subpath </td></tr>
-</table></td></tr></table>
-
-<P>
- To unconditionally access a zipped-file (as the counter-part of a
- zip-file's directory) you should be using the functions having a
- <code>zzip_file_</code> prefix which are the methods working on
- ZZIP_FILE pointers directly and assuming those are references of
- a zipped file with a ZZIP_DIR.
-</P>
-<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
- <tr><td width=50%> zzip_file_open </td>
- <td width=50%> open a file within a zip and prepare a zlib
- compressor for it - note the ZZIP_DIR argument,
- multiple ZZIP_FILE's may share the same central
- directory shadow.</td></tr>
- <tr><td width=50%> zzip_file_close </td>
- <td width=50%> close the handle of zippedfile
- and free zlib compressor of it</td></tr>
- <tr><td width=50%> zzip_file_read </td>
- <td width=50%> decompress the next part of a compressed file
- within a zip-file</td></tr>
-</table></td></tr></table>
-<P>
- From here it is only a short step to the magic wrappers for
- file-access - when being given a filepath to zzip_open then
- the filepath is checked first for being possibly a real file
- (we can often do that by a <code>stat</code> call) and if there is
- a real file under that name then the returned ZZIP_FILE is
- nothing more than a wrapper around a file-descriptor of the
- underlying operating system. Any other calls like zzip_read
- will see the realfd-flag in the ZZIP_FILE and forward the
- execution to the read() function of the underlying operating system.
-</P>
-
-<P>
- However if that fails then the filepath is cut at last directory
- separator, i.e. a filepath of "this/test/README" is cut into the
- dir-part "this/test" and a file-part "README". Then the possible
- zip-extensions are attached (".zip" and ".ZIP") and we check if
- there is a real file under that name. If a file "this/test.zip"
- does exist then it is given to zzip_dir_open which will create
- a ZZIP_DIR instance of it, and when that was successul (so it
- was in zip-format) then we call zzip_file_open which will see
- two arguments - the just opened ZZIP_DIR and the file-part. The
- resulting ZZIP_FILE has its own copy of a ZZIP_DIR, so if you
- open multiple files from the same zip-file than you will also
- have multiple in-memory copies of the zip's central directory
- whereas otherwise multiple ZZIP_FILE's may share a common
- ZZIP_DIR when being opened with zzip_file_open directly - the
- zzip_file_open's first argument is the ZZIP_DIR and the second
- one the file-part to be looked up within that zip-directory.
-</P>
-
-<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
- <tr><td width=50%> zzip_open </td>
- <td width=50%> try the file-path as a real-file, and if not
- there, look for the existance of ZZIP_DIR by
- applying extensions, and open the file
- contained within that one.</td></tr>
- <tr><td width=50%> zzip_close </td>
- <td width=50%> if the ZZIP_FILE wraps a real-file, then call
- read(), otherwise call zzip_file_read() </td></tr>
- <tr><td width=50%> zzip_close </td>
- <td width=50%> if the ZZIP_FILE wraps a real-file, then call
- close(), otherwise call zzip_file_close() </td></tr>
-</table></td></tr></table>
-
-<P>
- Up to here we have the original functionality of the zziplib
- when I (Guido Draheim) created the magic functions around the work from
- Tomi Ollila who wrote the routines to read and decompress files from
- a zip archive - unlike other libraries it was quite readable and
- intelligible source code (after many changes there is not much
- left of the original zip08x source code but that's another story).
- Later however some request and proposals and patches were coming in.
-</P>
-
-<P>
- Among the first extensions was the recursive zzip_open magic. In
- the first instance, the library did just do as described above:
- a file-path of "this/test/README" might be a zip-file known as
- "this/test.zip" containing a compressed file "README". But if
- there is neither a real file "this/test/README" and no real
- zip-file "this/test.zip" then the call would have failed but
- know the zzip_open call will recursivly check the parent
- directories - so it can now find a zip-file "this.zip" which
- contains a file-part "test/README".
-</P>
-
-<P>
- This dissolves the original meaning of a ZZIP_DIR and it has lead
- to some confusion later on - you can not create a DIRENT-like handle
- for "this/test/" being within a "test.zip" file. And actually, I did
- never see a reason to implement it so far (open "this.zip" and set
- an initial subpath of "test" and let zzip_readdir skip all entries
- that do not start with "test/"). This is left for excercie ;-)
-</P>
-
-<h3> Extras </h3>
-
-<P>
- The next requests circulated around other file-extensions to
- automagically look inside filetypes that have zip-format too but
- carry other fileextensions - most famous might be the ".PK3"
- files of ID's Quake game. There have been a number of these
- requests and in a lot of cases it dawned to me that those guys
- may have overlooked the zzip_dir_open functions to travel
- through documents of zipformat under any name - that is that the
- "magic" was not actually needed but they just wanted to read
- files in zipformat with the zziplib.
-</P>
-
-<P>
- Other requests circulated around encryption but I did reject
- those bluntly, always. Instead there have been always examples
- for doing some obfuscation around the zip-format so that the
- stock zip/unzip tools do not recognize them but a game
- software developer can pack/unpack his AI scripts and bitmaps
- into such a zipformat-like file.
-</P>
-
-<P>
- After some dead-end patches (being shipped along with the
- zziplib as configure-time compile-options - greetings to
- Lutz Sammer and Andreas Schiffler), the general approach
- of _ext_io came up, and finally implemented (greetings go
- to Mike Nordell). The _open()-calls do now each have a
- cousin of _open_ext_io() with two/three additional arguments
- being a set of extensions to loop through our magic testing,
- a callback-handler plugin-table for obfuscation-means,
- and (often) a bit-mask for extra-options - this bitmask even
- has "PREFERZIP" and "ONLYZIP" options to skip the real-file
- test magic in those <code>zzip_*open</code> functions.
-</P>
-
-<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
- <tr><td width=50%> zzip_open(name,flags) </td>
- <td width=50%> zzip_open_ext_io(name,flags,mode,ext,io) </td></tr>
- <tr><td width=50%> zzip_opendir(name) </td>
- <td width=50%> zzip_opendir_ext_io(name,mode,ext,io) </td></tr>
- <tr><td width=50%> zzip_dir_open(name,errp) </td>
- <td width=50%> zzip_dir_open_ext_io(name,errp,ext,io) </td></tr>
- <tr><td width=50%> zzip_dir_fdopen(fd,errp) </td>
- <td width=50%> zzip_dir_fdopen_ext_io(fd,errp,ext,io) </td></tr>
- <tr><td width=50%> zzip_file_open(dir,name,mode) </td>
- <td width=50%> zzip_file_open_ext_io(dir,name,mode,ext,io) </td></tr>
-</table></td></tr></table>
-
-<P>
- Oh, and note that the mode,ext,io extras are memorized
- in the respecitive ZZIP_DIR handle attached, so each
- of the other calls like <code>zzip_file_open()</code>
- and <code>zzip_read()</code> will be using them. There
- are a few helper routines to help setup a new io-plugin
- where the init_io will currently just memcopy the
- default_io entries into the user-supplied plugin-struct.
-</P>
-
-<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
- <tr><td width=50%> zzip_init_io </td>
- <td width=50%> the recommended way to do things </td></tr>
- <tr><td width=50%> zzip_get_default_io </td>
- <td width=50%> used internally whenever you supply a null
- for the io-argument of a _ext_io()-call </td></tr>
- <tr><td width=50%> zzip_get_default_ext </td>
- <td width=50%> used internally but not exported </td></tr>
-</table></td></tr></table>
-
-
-<P>
- And last some stdio-like replacements were build but these
- happen to be actually just small wrappers around the other
- posix-like magic-calls. It just offers some convenience
- since wrappers like "SDL_rwops" tend to use a stringised
- open-mode - and I took the occasion to fold the zzip-bits
- for the _ext_io-calls right in there recognized via
- special extensions to the openmode-string of zzip_fopen().
-</P>
-
-<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
- <tr><td width=50%> zzip_fopen </td>
- <td width=50%> convert stringmode and call zzip_open_ext_io </td></tr>
- <tr><td width=50%> zzip_fread </td>
- <td width=50%> slower way to say zzip_read </td></tr>
- <tr><td width=50%> zzip_fclose </td>
- <td width=50%> a synonym of zzip_close </td></tr>
-</table></td></tr></table>
-
-<P>
- For some reason, people did need the full set of function-calls()
- to be working on zzip-wrappers too, so here they are - if the
- ZZIP_FILE instance did wrap a real file, then the real posix-call
- will be used, otherwise it is simulated on the compressed stream
- with a zip-contained file - especially <code>seek()</code> can be
- a slow operation:
- if the new point is later then just read out more bytes till we
- hit that position but if it is an earlier point then rewind to the
- beginning of the compressed data and start reading/decompression
- until the position is met.
-</P>
-
-<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
- <tr><td width=50%> zzip_rewind </td>
- <td width=50%> magic for rewind() </td></tr>
- <tr><td width=50%> zzip_tell </td>
- <td width=50%> magic for tell() </td></tr>
- <tr><td width=50%> zzip_seek </td>
- <td width=50%> magic for seek() </td></tr>
-</table></td></tr></table>
-
-<P>
- And last not least, there are few informative functions to
- use function-calls to read parts of the opaque structures
- of zzip-objects and their zzip-factory.
-</P>
-
-<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
- <tr><td width=50%> zzip_dir_stat </td>
- <td width=50%> a stat()-like thing on a file within a ZZIP_DIR </td></tr>
- <tr><td width=50%> zzip_dir_real </td>
- <td width=50%> check if ZZIP_DIR wraps a stat'able posix-dirent</td></tr>
- <tr><td width=50%> zzip_file_real </td>
- <td width=50%> check if ZZIP_FILE wraps a stat'able posix-file </td></tr>
- <tr><td width=50%> zzip_realdir </td>
- <td width=50%> if zzip_dir_real then return the posix-dirent </td></tr>
- <tr><td width=50%> zzip_realfd </td>
- <td width=50%> if zzip_file_real then return the posix-file </td></tr>
- <tr><td width=50%> zzip_dirhandle </td>
- <td width=50%> the attached ZZIP_DIR of compressed ZZIP_FILE </td></tr>
- <tr><td width=50%> zzip_dirfd </td>
- <td width=50%> the attached posix-file of ZZIP_DIR zip-file </td></tr>
- <tr><td width=50%> zzip_set_error </td>
- <td width=50%> set the last ZZIP_DIR error-code </td></tr>
- <tr><td width=50%> zzip_error </td>
- <td width=50%> get the last ZZIP_DIR error-code </td></tr>
- <tr><td width=50%> zzip_strerror </td>
- <td width=50%> convert a zzip_error into a readable string </td></tr>
- <tr><td width=50%> zzip_strerror_of </td>
- <td width=50%> combine both above zzip_strerror of zzip_error </td></tr>
- <tr><td width=50%> zzip_errno </td>
- <td width=50%> helper to wrap a zzip-error to a posix-errno </td></tr>
- <tr><td width=50%> zzip_compr_str </td>
- <td width=50%> helper to wrap a compr-number to a readable string
- </td></tr>
- <tr><td width=50%> zzip_dir_free </td>
- <td width=50%> internally called by zzip_dir_close if the ref-count
- of the ZZIP_DIR has gone zero</td></tr>
- <tr><td width=50%> zzip_freopen </td>
- <td width=50%> to reuse the ZZIP_DIR from another ZZIP_FILE so it does
- not need to be parsed again </td></tr>
- <tr><td width=50%> zzip_open_shared_io </td>
- <td width=50%> the ext/io cousin but it does not close the old ZZIP_FILE
- and instead just shares the ZZIP_DIR if possible</td></tr>
-</table></td></tr></table>
-
+ The zzip library was orginally developped by Tomi Ollila as a
+ set of zip decoder routines. Guido Draheim did pick it up and
+ wrapped them under a call synopsis matching their posix
+ api calls. Therefore <code>zzip_open()</code> has the same
+ synopsis as <code>open(2)</code> but it can open zipped files.
+ Later the distinction was made between magic wrappers and apis
+ for direct access to zip archives and the files contained
+ in the archive.
+</P>
+<P>
+ These (three) functional apis have little helper functions
+ alongside including those to get the posix filehandle out of a
+ zzip handle and to get some attributes about the data handle
+ represented by a zzip handle. Plus checking for error codes
+ that may have been generated from internal checks.
+</P>
+
+<dl>
+<dt> <a href="zzip-basics.html">Basics</a> </dt>
+<dd> Magic Wrappers, Zip Archive Dir access, Zipped File access </dd>
+<dt> <a href="zzip-extras.html">Extras</a> </dt>
+<dd> ext/io init, StdC calls, Error defs, ReOpen, FileStat </dd>
+</dl>
--- /dev/null
+<h2> ZZIP API Basics </h2> The open/close API description.
+
+<!--border--> <date> 20. July 2002 </date>
+
+<h3> Basics </h3>
+
+<P>
+ The naming schem of functions in this library follow a simple rule:
+ if you see a function with a <code>zzip_</code> prefix followed by
+ compact name representing otherwise a C library or posix function then
+ it is a magic wrapper that can automagically handle both real
+ files/directories or zip-contained files. This includes:
+</P>
+<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
+ <tr><td width=50%> zzip_opendir </td><td width=50%> opendir </td></tr>
+ <tr><td width=50%> zzip_readdir </td><td width=50%> readdir </td></tr>
+ <tr><td width=50%> zzip_closedir </td><td width=50%> closedir </td></tr>
+ <tr><td width=50%> zzip_rewinddir </td><td width=50%> rewinddir </td></tr>
+ <tr><td width=50%> zzip_telldir </td><td width=50%> telldir </td></tr>
+ <tr><td width=50%> zzip_seekdir </td><td width=50%> seekdir </td></tr>
+</table></td></tr></table>
+<P>
+ The ZZIP_DIR handle can wrap both a real directory or a zip-file.
+ Note that you can not open a virtual directory <em>within</em> a
+ zip-file, the ZZIP_DIR is either a real DIR-handle of a real
+ directory or the reference of ZIP-file but never a DIR-handle
+ within a ZIP-file - there is no such schema of a SUB-DIR handle
+ implemented in this library. A ZZIP_DIR does actually represent
+ the central directory of a ZIP-file, so that each file entry in
+ this ZZIP-DIR can possibly have a subpath prepended.
+</P>
+
+<P>
+ This form of magic has historic reasons as originally the
+ magic wrappers of this library were not meant to wrap a complete
+ subtree of a real file tree but only a single directory being
+ wrapped with into a zip-file and placed instead. Later proposals
+ and patches were coming in to support subtree wrapping by not
+ only making a split between the dir-part and file-part but
+ going recursivly up through all "/"-dirseparators of a filepath
+ given to <code>zzip_open</code> and looking for zip-file there.
+</P>
+
+<P>
+ To open a zip-file unconditionally one should be using their
+ respective methods that would return a ZZIP_DIR handle being
+ the representant memory instance of a ZIP-DIR, the central
+ directory of a zip-file. From that ZZIP-DIR one can open a
+ compressed file entry which will be returned as a ZZIP_FILE
+ pointer.
+</P>
+<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
+ <tr><td width=50%> zzip_dir_open </td>
+ <td width=50%> open a zip-file and parse the central directory
+ to a memory shadow</td></tr>
+ <tr><td width=50%> zzip_dir_close </td>
+ <td width=50%> close a zip-file and free the memory shadow</td></tr>
+ <tr><td width=50%> zzip_dir_fdopen </td>
+ <td width=50%> aquire the given posix-file and try to parse it
+ as a zip-file.</td></tr>
+ <tr><td width=50%> zzip_dir_read </td>
+ <td width=50%> return the next info entry of a zip-file's central
+ directory - this would include a possible subpath </td></tr>
+</table></td></tr></table>
+
+<P>
+ To unconditionally access a zipped-file (as the counter-part of a
+ zip-file's directory) you should be using the functions having a
+ <code>zzip_file_</code> prefix which are the methods working on
+ ZZIP_FILE pointers directly and assuming those are references of
+ a zipped file with a ZZIP_DIR.
+</P>
+<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
+ <tr><td width=50%> zzip_file_open </td>
+ <td width=50%> open a file within a zip and prepare a zlib
+ compressor for it - note the ZZIP_DIR argument,
+ multiple ZZIP_FILE's may share the same central
+ directory shadow.</td></tr>
+ <tr><td width=50%> zzip_file_close </td>
+ <td width=50%> close the handle of zippedfile
+ and free zlib compressor of it</td></tr>
+ <tr><td width=50%> zzip_file_read </td>
+ <td width=50%> decompress the next part of a compressed file
+ within a zip-file</td></tr>
+</table></td></tr></table>
+<P>
+ From here it is only a short step to the magic wrappers for
+ file-access - when being given a filepath to zzip_open then
+ the filepath is checked first for being possibly a real file
+ (we can often do that by a <code>stat</code> call) and if there is
+ a real file under that name then the returned ZZIP_FILE is
+ nothing more than a wrapper around a file-descriptor of the
+ underlying operating system. Any other calls like zzip_read
+ will see the realfd-flag in the ZZIP_FILE and forward the
+ execution to the read() function of the underlying operating system.
+</P>
+
+<P>
+ However if that fails then the filepath is cut at last directory
+ separator, i.e. a filepath of "this/test/README" is cut into the
+ dir-part "this/test" and a file-part "README". Then the possible
+ zip-extensions are attached (".zip" and ".ZIP") and we check if
+ there is a real file under that name. If a file "this/test.zip"
+ does exist then it is given to zzip_dir_open which will create
+ a ZZIP_DIR instance of it, and when that was successul (so it
+ was in zip-format) then we call zzip_file_open which will see
+ two arguments - the just opened ZZIP_DIR and the file-part. The
+ resulting ZZIP_FILE has its own copy of a ZZIP_DIR, so if you
+ open multiple files from the same zip-file than you will also
+ have multiple in-memory copies of the zip's central directory
+ whereas otherwise multiple ZZIP_FILE's may share a common
+ ZZIP_DIR when being opened with zzip_file_open directly - the
+ zzip_file_open's first argument is the ZZIP_DIR and the second
+ one the file-part to be looked up within that zip-directory.
+</P>
+
+<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
+ <tr><td width=50%> zzip_open </td>
+ <td width=50%> try the file-path as a real-file, and if not
+ there, look for the existance of ZZIP_DIR by
+ applying extensions, and open the file
+ contained within that one.</td></tr>
+ <tr><td width=50%> zzip_close </td>
+ <td width=50%> if the ZZIP_FILE wraps a real-file, then call
+ read(), otherwise call zzip_file_read() </td></tr>
+ <tr><td width=50%> zzip_close </td>
+ <td width=50%> if the ZZIP_FILE wraps a real-file, then call
+ close(), otherwise call zzip_file_close() </td></tr>
+</table></td></tr></table>
+
+<P>
+ Up to here we have the original functionality of the zziplib
+ when I (Guido Draheim) created the magic functions around the work from
+ Tomi Ollila who wrote the routines to read and decompress files from
+ a zip archive - unlike other libraries it was quite readable and
+ intelligible source code (after many changes there is not much
+ left of the original zip08x source code but that's another story).
+ Later however some request and proposals and patches were coming in.
+</P>
+
+<P>
+ Among the first extensions was the recursive zzip_open magic. In
+ the first instance, the library did just do as described above:
+ a file-path of "this/test/README" might be a zip-file known as
+ "this/test.zip" containing a compressed file "README". But if
+ there is neither a real file "this/test/README" and no real
+ zip-file "this/test.zip" then the call would have failed but
+ know the zzip_open call will recursivly check the parent
+ directories - so it can now find a zip-file "this.zip" which
+ contains a file-part "test/README".
+</P>
+
+<P>
+ This dissolves the original meaning of a ZZIP_DIR and it has lead
+ to some confusion later on - you can not create a DIRENT-like handle
+ for "this/test/" being within a "test.zip" file. And actually, I did
+ never see a reason to implement it so far (open "this.zip" and set
+ an initial subpath of "test" and let zzip_readdir skip all entries
+ that do not start with "test/"). This is left for excercie ;-)
+</P>
--- /dev/null
+<h2> ZZIP API extras </h2> The check/init API description.
+
+<!--border--> <date> 20. July 2002 </date>
+
+<h3> Extras </h3>
+
+<P>
+ The next requests circulated around other file-extensions to
+ automagically look inside filetypes that have zip-format too but
+ carry other fileextensions - most famous might be the ".PK3"
+ files of ID's Quake game. There have been a number of these
+ requests and in a lot of cases it dawned to me that those guys
+ may have overlooked the zzip_dir_open functions to travel
+ through documents of zipformat under any name - that is that the
+ "magic" was not actually needed but they just wanted to read
+ files in zipformat with the zziplib.
+</P>
+
+<P>
+ Other requests circulated around encryption but I did reject
+ those bluntly, always. Instead there have been always examples
+ for doing some obfuscation around the zip-format so that the
+ stock zip/unzip tools do not recognize them but a game
+ software developer can pack/unpack his AI scripts and bitmaps
+ into such a zipformat-like file.
+</P>
+
+<P>
+ After some dead-end patches (being shipped along with the
+ zziplib as configure-time compile-options - greetings to
+ Lutz Sammer and Andreas Schiffler), the general approach
+ of _ext_io came up, and finally implemented (greetings go
+ to Mike Nordell). The _open()-calls do now each have a
+ cousin of _open_ext_io() with two/three additional arguments
+ being a set of extensions to loop through our magic testing,
+ a callback-handler plugin-table for obfuscation-means,
+ and (often) a bit-mask for extra-options - this bitmask even
+ has "PREFERZIP" and "ONLYZIP" options to skip the real-file
+ test magic in those <code>zzip_*open</code> functions.
+</P>
+
+<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
+ <tr><td width=50%> zzip_open(name,flags) </td>
+ <td width=50%> zzip_open_ext_io(name,flags,mode,ext,io) </td></tr>
+ <tr><td width=50%> zzip_opendir(name) </td>
+ <td width=50%> zzip_opendir_ext_io(name,mode,ext,io) </td></tr>
+ <tr><td width=50%> zzip_dir_open(name,errp) </td>
+ <td width=50%> zzip_dir_open_ext_io(name,errp,ext,io) </td></tr>
+ <tr><td width=50%> zzip_dir_fdopen(fd,errp) </td>
+ <td width=50%> zzip_dir_fdopen_ext_io(fd,errp,ext,io) </td></tr>
+ <tr><td width=50%> zzip_file_open(dir,name,mode) </td>
+ <td width=50%> zzip_file_open_ext_io(dir,name,mode,ext,io) </td></tr>
+</table></td></tr></table>
+
+<P>
+ Oh, and note that the mode,ext,io extras are memorized
+ in the respecitive ZZIP_DIR handle attached, so each
+ of the other calls like <code>zzip_file_open()</code>
+ and <code>zzip_read()</code> will be using them. There
+ are a few helper routines to help setup a new io-plugin
+ where the init_io will currently just memcopy the
+ default_io entries into the user-supplied plugin-struct.
+</P>
+
+<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
+ <tr><td width=50%> zzip_init_io </td>
+ <td width=50%> the recommended way to do things </td></tr>
+ <tr><td width=50%> zzip_get_default_io </td>
+ <td width=50%> used internally whenever you supply a null
+ for the io-argument of a _ext_io()-call </td></tr>
+ <tr><td width=50%> zzip_get_default_ext </td>
+ <td width=50%> used internally but not exported </td></tr>
+</table></td></tr></table>
+
+
+<P>
+ And last some stdio-like replacements were build but these
+ happen to be actually just small wrappers around the other
+ posix-like magic-calls. It just offers some convenience
+ since wrappers like "SDL_rwops" tend to use a stringised
+ open-mode - and I took the occasion to fold the zzip-bits
+ for the _ext_io-calls right in there recognized via
+ special extensions to the openmode-string of zzip_fopen().
+</P>
+
+<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
+ <tr><td width=50%> zzip_fopen </td>
+ <td width=50%> convert stringmode and call zzip_open_ext_io </td></tr>
+ <tr><td width=50%> zzip_fread </td>
+ <td width=50%> slower way to say zzip_read </td></tr>
+ <tr><td width=50%> zzip_fclose </td>
+ <td width=50%> a synonym of zzip_close </td></tr>
+</table></td></tr></table>
+
+<P>
+ For some reason, people did need the full set of function-calls()
+ to be working on zzip-wrappers too, so here they are - if the
+ ZZIP_FILE instance did wrap a real file, then the real posix-call
+ will be used, otherwise it is simulated on the compressed stream
+ with a zip-contained file - especially <code>seek()</code> can be
+ a slow operation:
+ if the new point is later then just read out more bytes till we
+ hit that position but if it is an earlier point then rewind to the
+ beginning of the compressed data and start reading/decompression
+ until the position is met.
+</P>
+
+<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
+ <tr><td width=50%> zzip_rewind </td>
+ <td width=50%> magic for rewind() </td></tr>
+ <tr><td width=50%> zzip_tell </td>
+ <td width=50%> magic for tell() </td></tr>
+ <tr><td width=50%> zzip_seek </td>
+ <td width=50%> magic for seek() </td></tr>
+</table></td></tr></table>
+
+<P>
+ And last not least, there are few informative functions to
+ use function-calls to read parts of the opaque structures
+ of zzip-objects and their zzip-factory.
+</P>
+
+<table cellpadding=10 width=100%><tr><td><table border=1 width=100%>
+ <tr><td width=50%> zzip_dir_stat </td>
+ <td width=50%> a stat()-like thing on a file within a ZZIP_DIR </td></tr>
+ <tr><td width=50%> zzip_dir_real </td>
+ <td width=50%> check if ZZIP_DIR wraps a stat'able posix-dirent</td></tr>
+ <tr><td width=50%> zzip_file_real </td>
+ <td width=50%> check if ZZIP_FILE wraps a stat'able posix-file </td></tr>
+ <tr><td width=50%> zzip_realdir </td>
+ <td width=50%> if zzip_dir_real then return the posix-dirent </td></tr>
+ <tr><td width=50%> zzip_realfd </td>
+ <td width=50%> if zzip_file_real then return the posix-file </td></tr>
+ <tr><td width=50%> zzip_dirhandle </td>
+ <td width=50%> the attached ZZIP_DIR of compressed ZZIP_FILE </td></tr>
+ <tr><td width=50%> zzip_dirfd </td>
+ <td width=50%> the attached posix-file of ZZIP_DIR zip-file </td></tr>
+ <tr><td width=50%> zzip_set_error </td>
+ <td width=50%> set the last ZZIP_DIR error-code </td></tr>
+ <tr><td width=50%> zzip_error </td>
+ <td width=50%> get the last ZZIP_DIR error-code </td></tr>
+ <tr><td width=50%> zzip_strerror </td>
+ <td width=50%> convert a zzip_error into a readable string </td></tr>
+ <tr><td width=50%> zzip_strerror_of </td>
+ <td width=50%> combine both above zzip_strerror of zzip_error </td></tr>
+ <tr><td width=50%> zzip_errno </td>
+ <td width=50%> helper to wrap a zzip-error to a posix-errno </td></tr>
+ <tr><td width=50%> zzip_compr_str </td>
+ <td width=50%> helper to wrap a compr-number to a readable string
+ </td></tr>
+ <tr><td width=50%> zzip_dir_free </td>
+ <td width=50%> internally called by zzip_dir_close if the ref-count
+ of the ZZIP_DIR has gone zero</td></tr>
+ <tr><td width=50%> zzip_freopen </td>
+ <td width=50%> to reuse the ZZIP_DIR from another ZZIP_FILE so it does
+ not need to be parsed again </td></tr>
+ <tr><td width=50%> zzip_open_shared_io </td>
+ <td width=50%> the ext/io cousin but it does not close the old ZZIP_FILE
+ and instead just shares the ZZIP_DIR if possible</td></tr>
+</table></td></tr></table>
+
* Guido Draheim <guidod@gmx.de>
* Tomi Ollila <Tomi.Ollila@iki.fi>
*
- * Copyright (c) 1999,2000,2001,2002,2003 Guido Draheim
+ * Copyright (c) 1999,2000,2001,2002,2003,2004 Guido Draheim
* All rights reserved,
* usage allowed under the restrictions of the
* Lesser GNU General Public License
* zzip/file.c
*/
_zzip_export
-ZZIP_FILE * zzip_file_open(ZZIP_DIR * dir, zzip_char_t* name, int modes);
+ZZIP_FILE * zzip_file_open(ZZIP_DIR * dir, zzip_char_t* name, int flags);
_zzip_export
int zzip_file_close(ZZIP_FILE * fp);
_zzip_export
ZZIP_DIR * zzip_opendir_ext_io(zzip_char_t* name, int o_modes,
zzip_strings_t* ext, zzip_plugin_io_t io);
-_zzip_export
-ZZIP_FILE * zzip_file_open_ext_io(ZZIP_DIR * dir,
- zzip_char_t* name, int flags,
- zzip_strings_t* ext, zzip_plugin_io_t io);
-
_zzip_export
ZZIP_DIR * zzip_dir_open_ext_io(zzip_char_t* filename,
zzip_error_t* errcode_p,
zzip_strings_t* ext, zzip_plugin_io_t io);
+/* zzip_file_open_ext_io => zzip_dir_open_ext_io + zzip_file_open */
+
#if defined _ZZIP_WRITE_SOURCE
/* ........................................................................
* write support is not yet implemented
%define lib lib010
Summary: ZZipLib - libZ-based ZIP-access Library
Name: zziplib
-Version: 0.13.34
+Version: 0.13.35
Release: 1mdk
Serial: 1
Copyright: LGPL
projects / zziplib / commitdiff