On 7/20/06, Derick Rethans <[EMAIL PROTECTED]> wrote:
On Thu, 20 Jul 2006, Pierre wrote:
> Do you really ask me what Zip say?
You miss the point. If you do "new Zip" ... then I've no idea what the
object you get represents. However, doing "new ZipArchive" makes sense
as then you know the object represents a ZipArchive for example. Just
"Zip" doesn't say anything about the object so I consider it a bad
classname.
I have a good hundred (verbose) users (which mails me about it) out
there, for example one of them is Alexander Pak, Summer Of Code Open
Document project. They asked me many many things. One thing was to
bring consistency to the API, move to a stable state and... bundled
it as soon as possible. But they never had any kind of comments or
questions about what is "new Zip".
There will be more objects in the future, but not related directly to
the zip itself or its properties (no ZipFile object for example). I'm
thinking about iterators or helpers for complex operations. For these
classes, yes, it makes sense to name them ZipIteratorXxx or ZipFooBar.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
