> We could add support for this, but as the general consensus is that we'd much rather remove support for unsetting declared object properties (if we could cover the lazy loading use case in a different way), I don't think it makes sense to allow this.
Ok, thanks. Just wanted to double check. Note that I'm actually liking the ability to unset declared properties for 2 reasons: - lazy loading, as you mentioned - ability to differentiate between unloaded properties, and properties loaded as null from the database (useful in data mappers) Ben