Everything
php
Learn Community Releases The PHP Project
Home » Project » Newsgroups » php.internals » Re: ADT, SPL »

Re: ADT, SPL

php.internals

Stanislav Malyshev

23 years ago
SB>> > Can't it be done without keeping another copy of entire Zend engine? SB>> SB>> As Sterling already mentioned, it should be merged into Zend at some SB>> point in time, preferably before PHP 5 :) Ah. Well, then a brief intro into how it is meant to work and what it is meant to do would help a lot. I value very much the ability of all authors to write self-documenting and clear to understand code, but some explanations still might help. The full documentation would help a lot, especially if it goes into the engine.
-- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.109

Wez Furlong

23 years ago
[This is not a dig!] The same could be said about the engine code itself ;) --Wez. On Mon, 23 Jun 2003, Stanislav Malyshev wrote:

Stanislav Malyshev

23 years ago
WF>> The same could be said about the engine code itself ;) I see your point, but the rest of the engine does not need to be integrated with itself, it already is. Also, the parts of the engine that are exposed to the user are or will be (I hope) documented pretty well, just as user-exposed parts of ZE1 are documented. Also, if the engine documentation is not in the good state, this is not the reason to make it yet worse :)
-- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.109

Andi Gutmans

23 years ago
At 09:14 AM 6/23/2003 +0100, Wez Furlong wrote:
>[This is not a dig!] > >The same could be said about the engine code itself ;)
:) We do need some sort of email which explains the API and the semantics. For instance, I'm pretty sure I won't like the names of the interfaces :) spl_foreach is ugly as hell. Anyway, I'd be glad if we could have a very quick overview. Andi

Sebastian Bergmann

23 years ago
Andi Gutmans wrote:
> spl_foreach is ugly as hell.
What about ForeachIterator?
-- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ http://www.professionelle-softwareentwicklung-mit-php5.de/

Andi Gutmans

23 years ago
At 07:14 PM 6/23/2003 +0200, Sebastian Bergmann wrote:
>Andi Gutmans wrote: > > spl_foreach is ugly as hell. > > What about ForeachIterator?
And "Iterator"? :) Anyway, forget discussing names now. It'd be nice to see a short spec of what SPL does so that we can discuss it. Andi

(Marcus Börger)

23 years ago
Hello Andi, Monday, June 23, 2003, 8:14:30 PM, you wrote: AG> At 09:14 AM 6/23/2003 +0100, Wez Furlong wrote:
>>[This is not a dig!] >> >>The same could be said about the engine code itself ;)
AG> :) AG> We do need some sort of email which explains the API and the semantics. For AG> instance, I'm pretty sure I won't like the names of the interfaces :) AG> spl_foreach is ugly as hell. AG> Anyway, I'd be glad if we could have a very quick overview. The documentation is done in spl.phps, you'll find this file in the spl directory. And before namespaces were removed the names weren't that ugly. Anyway the names reflect what their classes and functions are doing. There is also a README file and an examples sub directory. But anyway i'll write something together and put it into README.
-- Best regards, Marcus mailto:helly@php.net

Andi Gutmans

23 years ago
At 08:33 PM 6/23/2003 +0200, Marcus Börger wrote:
>Hello Andi, > >Monday, June 23, 2003, 8:14:30 PM, you wrote: > >AG> At 09:14 AM 6/23/2003 +0100, Wez Furlong wrote: > >>[This is not a dig!] > >> > >>The same could be said about the engine code itself ;) > >AG> :) > >AG> We do need some sort of email which explains the API and the >semantics. For >AG> instance, I'm pretty sure I won't like the names of the interfaces :) >AG> spl_foreach is ugly as hell. >AG> Anyway, I'd be glad if we could have a very quick overview. > >The documentation is done in spl.phps, you'll find this file in the spl >directory. And before namespaces were removed the names weren't that ugly. >Anyway the names reflect what their classes and functions are doing. >There is also a README file and an examples sub directory. > >But anyway i'll write something together and put it into README.
I'll check it out when I have time. I think even with namespaces it still used spl, which IMO is ugly and not very understandable. Anyway, it doesn't matter because the naming convention is the least of my worries (right now). Andi