Hi Rasmus,
thanks for you reply. As some of the phpers already
stated I also disagree about the visibility issue. But
it's IMHO anyway (besides I do not have technical
skills enough to try to implement it).
I'll check the template you mentioned but I was
wondering if a "built-in" one would not give a better
integration and give php users a "standard" way...
So what's in the TODO list for a 4.1 release ?
Thanks again
--- Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
>
> For a fast templating system, see Smarty.
> http://www.phpinsider.com/php/code/Smarty/
>
> As for better OO. I think many of the things people
> ask for, like
> visibility (public,private,protected) class
> properties, aren't actually
> features that add functionality, but more just
> convenience features that
> could be implemented in user space.
>
> For example, you could establish a convention that
> said that any class
> property that starts with an _underscore should be
> considered a private
> property, and one would hope that your UML tool
> could be configured to
> understand that.
__________________________________________________
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
--
PHP General 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]
