Doc #64570 [Opn->Ver]: Phar::extractTo() documentation page has phar.readonly = 1stated as requrement

Edit report at https://bugs.php.net/bug.php?id=64570&edit=1 ID: 64570 Updated by: cmb@php.net Reported by: goran dot radulovic at gmail dot com Summary: Phar::extractTo() documentation page has phar.readonly = 1stated as requrement -Status: Open +Status: Verified Type: Documentation Problem -Package: Documentation problem +Package: PHAR related Operating System: MacOS X PHP Version: Irrelevant -Assigned To: +Assigned To: cmb Block user comment: N Private report: N New Comment: Indeed, that are ovbiously copy&paste errors. Previous Comments: ------------------------------------------------------------------------ [2013-04-02 23:49:24] goran dot radulovic at gmail dot com By mistake, i wrote "phar.readonly = 1", when in fact i meant to write "phar.readonly = 0" in bug title. Sorry ------------------------------------------------------------------------ [2013-04-02 23:32:05] goran dot radulovic at gmail dot com Description: ------------ --- From manual page: http://www.php.net/phar.extractto#refsect1-phar.extractto- description --- I don't see any particular reason for that requirement phar.readonly. I tried using this method with phar.readonly set to both 1 and 0 and in both cases it works perfectly. As for functionality, when using this method original phar file is not affected and modified in any way, and for that reason phar.readonly shoud not be relevant. Also on the same page, on method params section block. Description of the first metod parameter is 'Path within an archive to the file to delete.' which is also mistake. First parameter is destination directory, and extracing phar file to directory has nothing to do with deleting files. This leads me to conclusion that this is some mistake in documentation. However i must be sure before heavily relay on this method in our application. Thank you ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=64570&edit=1