> > * Semantic A is really confusing. e.g., > > var1.myproperty = var2.myproperty = y; > > who would have thought that var1.myproperty > > is different from var2.myproperty ?! > > It's only confusing for non well-behaving properties. The right solution > is to fix the property.
Ok. I concur. The confusing part is not really the chained assignment, but the abuse of property. For a confusingly defined property, even a simple assignment such as this var1.myproperty = var2.myproperty; can be nasty. Who would have expected (var1.myproperty == var2.myproperty) to be false after that assignment? So, I change my mind and go for Semantics A now. To be consistent, if a simple assignment is nasty, putting it into a chain shouldn't remove the nastiness. (Sorry for the nasty English) Nice day Nor Jaidi Tuah PRIVILEGED/CONFIDENTIAL information may be contained in this message. If you are neither the addressee (intended recipient) nor an authorised recipient of the addressee, and have received this message in error, please destroy this message (including attachments) and notify the sender immediately. STRICT PROHIBITION: This message, whether in part or in whole, should not be reviewed, retained, copied, reused, disclosed, distributed or used for any purpose whatsoever. Such unauthorised use may be unlawful and may contain material protected by the Official Secrets Act (Cap 153) of the Laws of Brunei Darussalam. DISCLAIMER: We/This Department/The Government of Brunei Darussalam, accept[s] no responsibility for loss or damage arising from the use of this message in any manner whatsoever. Our messages are checked for viruses but we do not accept liability for any viruses which may be transmitted in or with this message. _______________________________________________ vala-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/vala-list
