() Dmitry Antipov () Tue, 31 Jul 2012 17:50:43 +0400 > I think to do this well you will need separate macros for getting > and setting. Sure, but it's almost impossible to do this at once. Why? At the very beginning, it's possible to "overestimate" barrier assuming that each XVAR (obj, field) changes FIELD in OBJ; in the future, reads and writes may be separated, thus giving a precise write barrier. I think you're saying that you prefer to do: a1. substitute object access (whether LHS or RHS) w/ XVAR (obj, field) a2. distinguish LHS (which could benefit from optimization) from RHS a3. substitue LHS ‘XVAR (...) = value’ w/ SETVAR (obj, field, value) instead of: b1. distinguish LHS (which could benefit from optimization) from RHS b2. substitute LHS object access w/ SETVAR (obj, field, value) b3. substitute RHS object access w/ XVAR (obj, field) Is my understanding correct? -- Thien-Thi Nguyen ..................................... GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . . ACCEPT NO SUBSTITUTES . ........... please send technical questions to mailing lists ...........