On Fri, Nov 16, 2012 at 2:47 PM, Jan Ehrhardt <php...@ehrhardt.nl> wrote: > Sherif Ramadan in php.internals (Thu, 15 Nov 2012 21:23:48 -0500): >>People have been talking about and educating others about the >>deprecation of ext/mysql for quite some time now. I'm sure that it >>could be more clearly voiced from an official PHP Project stand-point, >>but we're down-playing the amount of education that has already gone >>underway here. > > Nevertheless, I had only a faint idea it was going to be deprecated. I > hardly ever look at the manual for the mysql_ functions because they > haven't changed for years. Re-using existing code just works. I think > you are overestimating the effect of those talks. >
Actually, I'm not. One of the reasons most people only know it's being deprecated in passing (your faint idea) is because there has been minimal action from the PHP Project on this. As you can see by the level of activity on this thread there is no real consensus on what should be done here. So the only action from the project so far has been inaction. The ones doing the informing are mostly speaking as individuals, whether they are core developers or not, developers of other PHP OSS frameworks/projects, they are basically divided. Their voices are not heard as one. But they are there and that's why people are aware of the deprecation to come. Obviously there is a benefit in standing united on this and making those voices heard more loudly and unanimously. The fact that you don't regularly look at the manual for functions you know by heart is one of the main arguments I'm making for adding E_DEPRECATED warnings to the mysql_connect/pconnect functions and why I'm advocating this RFC so vivaciously. I want developers, such as yourself, to have as much exposure as possible to the fact that the extension is being deprecated. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
