I've already demonstrated and explained what's wrong with strings. "Weird indirection" is what we have in every mainstream framework right now, where properties can be referenced only as strings - I gave a real-world example of this, and demonstrated with a practical example how the proposed feature can help improve on this issue.
I've demonstrated by example that this has more than limited scope. The fact that mainstream frameworks have to resort to strings for property-references is a symptom of the fact that this feature is absent: - Mainstream frameworks already do what I propose (using strings) demonstrating that it is a necessary task. - People use these frameworks - proving that developers want these features from the frameworks they use. Please, contribute something material to this discussion - your snappy responses have to make me think you're taking this very personally? I promise I'm not trying to ruin your day. Can't we just have a friendly discussion like grown-ups? On Tue, Apr 30, 2013 at 7:16 PM, Stas Malyshev <smalys...@sugarcrm.com>wrote: > Hi! > > > Any PHP dev who works with a mainstream framework does this daily, but > > the frameworks rely on strings for property-names. > > What's wrong with strings? Just because it doesn't have three levels of > objects on it, doesn't mean it's not OK to use it. > > > We now have static property-references, which means the codebase can be > > If you know the property, you can just access it, you don't need to > invent weird indirection for it. > > > Are we really going to quibble about syntax? This adds nothing to this > > We're going to quibble about again trying to bring very small scope and > exotic feature into the core of the language. > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 >
