On Wed, Apr 9, 2008 at 4:06 AM, Steph Fox <[EMAIL PROTECTED]> wrote: > This isn't how PHP used to be. This is a whole new way of coding, and you'd > like to force it onto people who never did that CS degree, but who coped > just fine until now. How sweet.
Right, however I think you underestimate the ability of our users to learn, but that's the least problem here. The main problem with the error code ways, using a return value or via extra function calls, is that they are never used or checked. Even the examples in the manual never use them. That's promoting bad practices and then users will wonder why their string look broken or empty. > Can I also point out that *every* uncaught exception is a fatal error? My example was not about not catching exceptions but about actually catch the possible exception. As I agree that exception can be confusing, their usage is this particular case is not that hard. > So please, yes, keep the procedural way as an option, make it possible for > people to use PHP without their having to be computer scientists first. The > moment the language loses that, it has nothing special to offer any more. Look at the syntax, there is no difference. One doesn't need to be a computer scientist to understand it. If we decide to keep the procedural API then let use a normal (and CS compliant .. well almost compliant) prefix. Using shorter names to spare a few key strokes is not a very good idea. number_format _ is better than numberfmt_. Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
