Re: PHP 4.0 Bug #6625 Updated: htmlspecialchars shouldescape"'" character

> Colin, Jon, Jon, Colin. He's been running this flamewar routine directly > on the dev list for a while now. (Do not feed the trolls) > Actually I wouldn't call Jon a troll. Trolls usually have no idea what they are talking about, Jon seems to be cognizant of the issues, whether he's right or wrong... Let me check with my lawyer before I comment. ;-) > Colin Viebrock wrote: > > Jon: > > > But you *are* an infantile moron. In what other manner should I treat you? > > Hah... gotta love Jon's ignorance of the "catching more flies with...." > concept. > Its funny I mentioned the same analogy to him in a private e-mail. Could there be any truth to that? Nah, we're moron developers, remember? > > > If the PHP team even slightly gave a damn about this sort of thing, then > > > they would invent and document a naming scheme for in-built functions. > > Obviously you have issues with more than just this particular bug/feature > > request. Join the dev mailing list and spout your vitriol there. > > This has been a recent topic of discussion on the dev list, actuallly. > A recent topic and a frequently discussed topic. I brought it up a while ago, other people have brought it up, there have been quite a few ideas. However, the only way I think this could be properly fixed (if it needs to be fixed at all) is to break backwards compatibilty. I'm going out on a limb here and saying the core developers are not that excited about that prospect. Perhaps it'll be addressed for PHP 5 or PHP 4.5... > > > I'm sorry, but as only one person against what seems to be a > > > horde of moronswith CVS write access, I fear the small good I could > > > do would be lost amongst the continuing damage caused by the rest > > > of you lot. > > He's been whining about the code of others, without making any sort > of significant contributions for a while. This is his MO, don't let > it shake you up. > What's that old saying, "Workers never talk and talkers never work" I don't know why that popped into my head. > > > You can close the conversation, but ignoring it won't close the issue. > > > The only way you can do that is by fixing it. I don't care - I'm through > > > trying to talk sense to people too stupid to even recognise it. > > Glad to hear it. > > Well then, I guess the issue will be open until one of the other stupid, > > moron PHP developers is convinced by your enlightened arguments that things > > need to change. I'll CC them on this, just to make sure they've heard you. > > He's already flogged his feature request on dev. I guess he figured he'd > try another angle at charming others with his brilliant repartee. :-) > I must admit, I take a morbid amusement at his comments, I guess its because I'm too stupid to understand them. -Sterling