Hi! > But what is "properly prefixed"? Is there a list of reserved prefixes?
Yes, it's called the manual :) > I agree. However, there are other "namespaces" which are not so > special, especially for beginners, for instance, array_* and str_*. And Adding something like strlen() in core now probably would be dangerous. array_* OTOH should be obvious as reserved. Just follow common sense - if you prefix your function the same way as a function group in the manual, then you're in trouble. > of course, someone might consider it to be reasonable to invent a new > function in userland which is an extension of some existing function, > therefore giving it a similar name, e.g. preg_replace_callback_array(). Someone would be wrong then. > Would that be considered to be bad style? If so, where is it documented? Yes. It is common sense. Not everything has to be spelled out to be true, and I think rule lawyering and ignoring common sense is not going to help anybody here. If you don't understand that adding preg_* function in global namespace that looks like existing core function is a bad idea, maybe some mentorship by more experienced developer is in order. > I'm aware that I'm nit-picking, and that the probability of such > collisions is near zero, but it is not equal to zero. If we limit ourselves only to changes that have exactly zero chance of affecting somebody's work however weird and broken that is, we may as well pack our things and go home, because we'd never do anything at all. I'm feeling that I am arguing with more and more bizzare scenarios invented for the purpose to arrive at predetermined conclusion instead of determining conclusion by real scenarios that sane developers do. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
