Hi People,
I'm not sure this is the right place to make a feature request, but here
goes..
I noticed some upgrades/ideas in the streams system lately.. Is there
any chance at all this can be migrated to an OOP system?
Here's the kind of think i would really like to see (java does it the
same way, more or less)
2 base stream interfaces
Writer
Reader
Which are implemented by:
FileWriter
FileReader
SocketWriter
SocketReader
StringWriter
StringReader
The Java IO library uses the decorator pattern to add functionality to
those base classes:
BufferedReader
BufferedWriter
HTMLFilterWriter
Since we are getting a new filter system, this could also be based on
this stream system....
This would allow be to write new base-classes for transports and make
use of all the existing filter-classes.
Also, this could be unified with XMLReader and XMLWriter and the SPL
file classes.
This implementation is just a suggestion (and I really like the
flexibility of the Java IO system).. I'm just really missing a proper
unified stream system..
Great work has already been done to centralize systems because of the
introduction of the Traversable interface and its descendants.. but more
and more often I find myself rewriting PHP extensions in PHP, because
there's no unified (abstracted) API..
I'm already pretty far in implementing this in PHP, and I would be more
than happy to PEAR it (if people are interested).. but I feel like a
system like this belongs at the core to prevent every new subsystem from
figuring out a new API...
I hope I made my point, I'll be more than happy to eloborate or help
writing specs for this system, my C skills are mediocre though..
Oh, and thanks for your great work.. PHP is the reason I can pay my rent
and I know there's a lot of people like me =)
Evert
Ilia Alshanetsky wrote:
Heh, Lukas preempted by e-mail a bit, but the bottom line is that the
next release in the 5.X series is going to be 5.2.0. Being a minor
version release we have a greater amount of freedom then the one we
normally get for patch level releases and that's exactly what we need
for some of the changed being planned. Basically for the next week, I
would like to assemble a list of changes (using Lukas' wiki) that we
wish to integrate into this release and then make a new branch. Once
that is the final list will be published and we will start on a 3
month release cycle, where the 1st month is allotted towards making
the big changes and the remaining 2 months to get things stable. So,
if you have changes you'd like to see in 5.2 (don't go too wild now
;-) ), reply to this e-mail.
On 2-May-06, at 6:07 AM, Lukas Smith wrote:
Hi,
I updated my phptodo wiki for the next planned release. Ilia also
send me a bunch of items that I threw on there:
http://oss.backendmedia.com/PhP52
If you want me to be your personal secretary let me know what items
you are missing from the list, what items should be assigned to
specific people and finally what items are completed.
regards,
Lukas
--PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Ilia Alshanetsky
Advanced Internet Designs Inc.
[EMAIL PROTECTED]
--PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
