At 17:52 3-6-2002, [EMAIL PROTECTED] shared with all of us: >The Zend engine is pretty strong, except for OO things, as it was not >designed with that in mind. Now I don't think OO is clutter, it's quite >nice, but IMO there are other things more important (for example the 1178 >open bug reports) then private methods.
+1. As a user, making web-applications and surrounding code, to tie stuff together I don't see, why 'better OO support' means adding private vars/methods. IMO this is indeed code clutter - if somebody decided to use a method marked as private in the comments, it's his problem. If people don't warn about a method being private the same applies. If you store plain-text passwords in your code, and claim security problem, you don't get the term security. Better OO support to me, means bringing down the overhead when using multiple instances, and the ability to declare static resource pointers in a parent class, so resources don't need to be re-opened, when an extended object instance is created. On another note - one of php's strengths that isn't mentioned, is x-platform development. Lately issues have arrived that break that (win32 mail, mac osx compilation, mkdir bsd segfault, resolver function detection) - if anything needs more focus, it's that selling point, because the 'run-anywhere' buzzword, is the one that sells to managers more than OO support. Yes - I'm aware that takes a lot of testing and people with access to different machines, which returns me to issue of involving QA more during development rather than at RC time. You can run automated tests, but can you run them on every platform you want to be able to support? Met vriendelijke groeten / With kind regards, IDG.nl Melvyn Sopacua Webmaster -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
