array ( 0 => 'index.php', 1 => 'PHP Manual', ), 'head' => array ( 0 => 'UTF-8', 1 => 'tr', ), 'this' => array ( 0 => 'phar.fileformat.zip.php', 1 => 'Zip-based phars', 2 => 'Zip-based phars', ), 'up' => array ( 0 => 'phar.fileformat.php', 1 => 'What makes a phar a phar and not a tar or a zip?', ), 'prev' => array ( 0 => 'phar.fileformat.tar.php', 1 => 'Tar-based phars', ), 'next' => array ( 0 => 'phar.fileformat.phar.php', 1 => 'Phar File Format', ), 'alternatives' => array ( ), 'source' => array ( 'lang' => 'en', 'path' => 'reference/phar/fileformat.xml', ), 'history' => array ( ), ); $setup["toc"] = $TOC; $setup["toc_deprecated"] = $TOC_DEPRECATED; $setup["parents"] = $PARENTS; manual_setup($setup); contributors($setup); ?>

Zip-based phars

Archives based on the zip file format support several features built into the zip file format. Per-file and whole-archive metadata is stored in the zip file comment and zip archive comment as a serialized string. Pre-existing zip comments will be successfully read as a string. Per-file compression read/write is supported with zlib DEFLATE compression, and read access is supported with bzip2 compression. There is no limit on the number of files within a zip-based phar archive. Empty directories are stored in the zip archive as files with a trailing slash like my/directory/