>> public property Hours read getHours write setHours; > > I actually like that, though I think we should support the whole > existing semantics, i.e. get/set/isset/unset. And probably keep the > names, so we don't call the same thing both "read" and "get".
This doesn't make sense. To call isset() on a property, would be to ask if the property itself exists. But once defined, a property always exists (think of methods, for example). (Sorry for sending again Stas, I forgot to reply all) - Dennis -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
