Re: PHP Alternative syntax

> Jeroen, > > With all due respect, you do not deprecate *anything* that is not within > your own code without having a clear, beyond-an-*un*reasonable-doubt > understanding that the development team is behind this deprecation. > > A quick glance over my php-dev archive reveals not even a faint trace of a > discussion regarding this issue. The discussion you refer to is a > 1984-style history change. "The online manual says it's deprecated, so it > is." Great, but who the heck changed the online manual? You did. Okay, I'm sorry that I noted it was deprecated, while I wasn't 100% about it. But I really had read it on the mailinglist, that people were saying so. I did assume people were following phpdoc commits, and since I didn't recieve any comments, I thought it was okay. I now know, and I aplogize once again, that no-comments definitely doesn't mean it's okay. There were quite a lot of old PHP3 things in the language section, including that false equals empty string, true doesn't exist and equals 1, etc etc. It was practically impossible to ask php-dev for everything, so I made logical assumptions every now and then. IMHO, the language section is quite improved, (though I'm still stuck in types, not further :-(... ) I made a wrong assumtion, based on uncomplete and apparently incorrect information, and I'm sorry. > I'm not going to address the actual issues you have with this feature, > because it has nothing to do with the bogus thing you did. Okay, I'll not start with that discussion either than. ;) > I haven't been following phpdoc commits lately, but if this hasn't been > removed, and moreover, clearly stated that contrary to prior > mis-documentation, this feature is not and will not be deprecated, please > fix the documentation today. You can use the same box you added for the > deprecation message, to display the message that it's not going anywhere. The documentation is already fixed a few days ago. I don't know wether it's a good place for a 'rectification', but I think it's indeed a good idea to re-add the warning box, with a text in the lines of: "This alternative syntax is particulary useful in including large chuncs of html. Be carefull with nesting alternative syntax. For normal code, {}-syntax is probably more clear (and more usual)" Comments? --Jeroen