Re: phar API
| From: | Lars Strojny | Date: | Fri, 28 Mar 2008 15:52:35 +0000 |
| Subject: | Re: phar API | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-36654@lists.php.net to get a copy of this message | ||
Hi everybody,
After having a great discussion with Marcus about the Phar API, I've
tried to sum up the proposed changes (of course with a strong focus on
my opinion about what should be changed :-)). The RFC is not yet
finished and I would like you to comment it beforehand. I've tried to
include as much as possible as discussed/proposed here. Also I would
like to help implementing it (up to the level where my skills end), so
this is not (only) about letting others work.
A few concrete questions:
Marcus, et al, could you please verify that my technical assumptions are
correct?
Elizabeth, et al, the concrete semantic of Phar::isWritable() is what?
Is it just is_writable('test.phar') or is it Phar::canWrite() &&
is_writable('test.phar')?
Benjamin, could you live with the proposed change of the ArrayAccess
usage?
The RFC: http://wiki.php.net/rfc/streamline-phar-api
cu, Lars
Attachment: [application/pgp-signature] Dies ist ein digital signierter Nachrichtenteil signature.asc
Attachment: [application/pgp-signature] Dies ist ein digital signierter Nachrichtenteil signature.asc