Hi,

It's nice having an out-of-the-box solution - everything just works
fine, just load the module (i.e. uncomment # in php.ini). Nevertheless,
who actually decides how a module's interface is designed? I know,
there are some guidelines, but this still ressembles too much to
anarchy in my eyes. What belongs into PEAR and what has to be done as
module? IMHO, a programming language gives the user essential basic
abilities, such as creating sockets, file system access, of course
providing a syntax, memory mangement etc.. and then it's up to the
PHP developer to create additional modules. This will provide better
transparency to the end-developer as he will be able to look at the
PEAR-sourcecodes and actually /understand/ what is being done. Why
does every PHP developer has to know C only to understand how such
modules work?

Too many modules were developed lately. Why not add a daniel-module
which only serves my needs, but goes into the main CVS tree?

Correct me, if I'm wrong. Your opinions please :)

Daniel Lorch

-----Ursprüngliche Nachricht-----
Von    : Daniel Lorch [mailto:[EMAIL PROTECTED]]
Datum  : Mittwoch, 5. Dezember 2001
Betreff: [PHP-DEV] [NEW EXTENSTION]: templates

Hi,

If I unterstood these guys correctly, they are developing a compiled
PHP-module (/ext/template/ or whatever). If ONE person decides to do
it, automatically some one else will not be able to contribute his
sourcecode, what is actually not a good thing. Maybe, Andrey Hristov's
code would be much better than the existing one, but it won't be
accepted because the other one has already become de facto standard of
PHP, and it's in the manual, nobody wants to change habits etc...

Kind Regards,
  Daniel Lorch

-----Ursprüngliche Nachricht-----
Von    : Martin Jansen [mailto:[EMAIL PROTECTED]]
Datum  : Mittwoch, 5. Dezember 2001
Betreff: [PHP-DEV] [NEW EXTENSTION]: templates

On Wed, 5 Dec 2001 15:15:29 +0100, Daniel Lorch wrote:

>it's nice to see that everyone wants to develop extensions for PHP,
>but why do these extension go all into the main CVS tree? why not keep
>PHP more modular?

New extension (ike the one, we are talking about) will go to PEAR
and will not be included in the main source tree (unless they
are extremely important). Or did I miss something?

- Martin



-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to