Date: 07/23/01
- Next message: giancarlo pinerolo: "Re: [phplib] Thoughts about Auth merging to PEAR"
- Previous message: Maxim Derkachev: "Re[2]: [phplib] [RFC] Future of phplib"
- In reply to: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Next in thread: Carlos Romero Mas: "RE: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
I have seen that PHPLIB is now on SourceForge.
I think it is a good thing but we now have to decide on a very important
topic : Coding standards !
Björn started to rewrite Template.inc using PEAR coding standards and Nathan
says he prefers the old way : get_var instead of getVar.
On the other hand, Stephan suggests we could use a wrapper class which name
will be something like this : Template-phplib.php that will extends
Template.php to make it compatible.
I agree with Björn and Stephan. Structure and good habits are very important
for efficient coding and code maintenance. PEAR coding standards will also
prove useful for documentation. I can tell because I use them in all my
projects now. It takes some time to get used to them but at the end they are
quite useful.
As a conclusion, I think PHPLIB should be rewritten in compliance with PEAR
coding standards and wrappers classes should be done for old code. This
would make PHPLIB to PEAR easier.
Bertrand Mansion
Mamasam
-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: giancarlo pinerolo: "Re: [phplib] Thoughts about Auth merging to PEAR"
- Previous message: Maxim Derkachev: "Re[2]: [phplib] [RFC] Future of phplib"
- In reply to: Dr Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Next in thread: Carlos Romero Mas: "RE: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

