Guys, you really hijacked this thread! But since you have... As an outsider to the property discussion, I feel that the key points are lost under a sea of quite spurious stuff. Here are the strong arguments as I see them:
1. The rationale for including @property with tight semantics is strong (mainly coming from disallowing property syntax on things which aren't properties). The rationale is doubtful with loose semantics that only disallows function syntax on properties. 2. Tight semantics prevent the use of the "fluent programming" idiom which is reasonably widely-used. 3. If we go with tight semantics, we break existing code. If we don't, we break TDPL. I'm seeing a fair bit of argument AGAINST tight semantics. But I'm seeing pretty much no argument FOR loose semantics. I'm not seeing any reason to choose loose semantics over D1 semantics. _______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
